I tried to explicitly load an extension via:
sqlite> select load_extension('mylib');
SQL error: no such function: load_extension
Is this because of the default setting of "enable_load_extension"?
http://www.sqlite.org/c3ref/enable_load_extension.html
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?
Assuming this *had* worked, I assume the shared library naming convention is
that of the dlopen library call, although this behavior may not jive
with Windows. Maybe it's like Java's LoadLibrary? i.e. ignore
the file extension (.so, .dll, .dylib) and drop the "lib" prefix.
e.g. to load "libmylib.dylib" on Mac, it's:
select load_extension('mylib');
...which would correspond to "libmylib.dll" on Windows, etc.
Is that how it is?
Can it be documented on this page? :
http://www.sqlite.org/lang_corefunc.html#load_extension
Thanks,
-Chris
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
