*** 50,53 **** --- 50,75 ---- </p> <p>Additional documentation is forthcoming...</p> + + <h2>Wish List</h2> + <li>Automatic loading of extension shared libraries when a database is first opened. This would benefit SQLite users that do not use the SQLite shell program, and only use the sqlite3 shared library. An sqlite specific table in each database loaded could be consulted with a list of shared library names to load. These extension shared libraries would not have paths or file suffixes (.dll or .so). The user would be expected to set up an appropriate search path via the native OS' shared library loading mechanism (PATH, LD_LIBRARY_PATH, or equivalent). The suffix would be determined at sqlite3 compile time to be .dll, .so, or whatever is appropriate for the platform. Such a table might look like this: + + <blockquote><pre> + <font color="#008000"> + create table sqlite_extensions ( + load INTEGER PRIMARY KEY, -- the order in which the extensions + -- are loaded and initialized + + name TEXT, -- name of the extension shared library. + -- Note: both the path and suffix is NOT to be included in name. + + init TEXT, -- name of the shared library entry point init function + + fini TEXT -- name of the shared library entry point unload function. + -- shared library unloading will be in the reverse order + -- of loading. + ); + </font> + </pre></blockquote> + </html>
Small. Fast. Reliable.
Choose any three.
Choose any three.
|
|