Automatically Load Statically Linked Extensions

*** DRAFT ***

SQLite C Interface

Automatically Load Statically Linked Extensions

int sqlite3_auto_extension(void(*xEntryPoint)(void));

R-23980-43280:[This interface causes the xEntryPoint() function to be invoked for each new database connection that is created. ] The idea here is that xEntryPoint() is the entry point for a statically linked SQLite extension that is to be automatically loaded into all new database connections.

R-59963-05629:[Even though the function prototype shows that xEntryPoint() takes no arguments and returns void, SQLite invokes xEntryPoint() with three arguments and expects an integer result as if the signature of the entry point where as follows:

   int xEntryPoint(
     sqlite3 *db,
     const char **pzErrMsg,
     const struct sqlite3_api_routines *pThunk
   );

]

If the xEntryPoint routine encounters an error, it should make *pzErrMsg point to an appropriate error message (obtained from sqlite3_mprintf()) and return an appropriate error code. R-40045-04159:[SQLite ensures that *pzErrMsg is NULL before calling the xEntryPoint(). ] R-61815-26679:[SQLite will invoke sqlite3_free() on *pzErrMsg after xEntryPoint() returns. ] R-45318-21719:[If any xEntryPoint() returns an error, the sqlite3_open(), sqlite3_open16(), or sqlite3_open_v2() call that provoked the xEntryPoint() will fail. ]

R-29907-62378:[Calling sqlite3_auto_extension(X) with an entry point X that is already on the list of automatic extensions is a harmless no-op. ] R-47326-42054:[No entry point will be called more than once for each database connection that is opened. ]

See also lists of Objects, Constants, and Functions.

*** DRAFT ***