WikiSysop: imported from WiKit id 57

2002-07-17T17:15:47Z

imported from WiKit id 57

New page

Here is the list of Frequently Asked Questions (FAQ) for the Panoptic MySQL driver for AOLserver, or, [[nsmysql]].

----

'''General nsmysql Questions:'''

'''Q: Why are table names being prepended to the column names in my result set?'''

'''A:''' Dumb decision that was made around v0.5 and v0.6. To turn the behavior off, change the following line in mysql.c:

static int include_tablenames = 1;

to

static int include_tablenames = 0;

Sorry about that.

----

'''Win32 Related Questions:'''

'''Q: I get this strange "win32 error code: 126" error in my server.log. What does it mean?'''

'''A:''' You're seeing something like this in your server log:

Warning: modload: failed to load 'x:/path/to/aolserver/bin/nsmysql.so': 'Win32 error code 126'

Error 126 is MOD_NOT_FOUND. Does nsmysql.so exist in the directory specified by x:/path/to/aolserver/bin?

'''Q: I get this strange "win32 error code: 1157" error in my server.log. What does it mean?'''

'''A:''' You're seeing something like this in your server log:

Notice: loading: x:/path/to/aolserver/bin/nsmysql.so
Warning: could not load x:/path/to/aolsever/bin/nsmysql.so: win32 error code: 1157
Error: nsd.db: could not load driver: mysql

Chances are, this means you didn't copy the libmySQL.dll into your
aolserver/bin directory. This is LoadLibrary()'s way of saying that
there were unresolved symbols when trying to dynamically load
nsmysql.so, which is a DLL. nsmysql.so is linked against libmySQL.dll,
therefore it too needs to be loadable, and the easiest way to do this
is to stick it in the aolserver/bin directory.

Nsmysql FAQ - Revision history

WikiSysop: imported from WiKit id 57