-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/12/2010 09:08 AM, Chris Wolf wrote: > If so, does that mean we can't use the out-of-the box shell and must > re-compile with a 'C' code change to invoke this? If that's true, why wasn't > this > simply controlled via an environment variable?
C code has to enable extension loading. If you use the SQLite shell then it always calls the C function to enable extension loading. Remember that SQLite is always a library in part of a larger process. It is up to that process to decide policy on extension with the safe default being to have it disabled. > Assuming this *had* worked, I assume the shared library naming convention is > that of the dlopen library call, Correct. Look for UnixDlOpen and WinDlOpen in the SQLite source where you see that they just directly call dlopen and LoadLibraryW. To my knowledge there is no convention for file names for SQLite extensions. My test extension has the imaginative filename under all operating systems of testextension.sqlext. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzdhfUACgkQmOOfHg372QT9AACcDS4Qmtoc93lggQyF5krhMThq Db8An24hI6UDBNwuazQjEHeUqmbcc3MR =+B/F -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
