Re: [sqlite] Is sqlite3_auto_extension() same compilation unit ruled out?

gt; Subject: Re: [sqlite] Is sqlite3_auto_extension() same compilation unit > ruled out? > > Have a look at the way readfile() and writefile() is implemented in the > sqlite interpreter. > > On Tue, Jun 13, 2017 at 10:38 AM, petern < > <mailto:peter.nichvolo...@gmai

Re: [sqlite] Is sqlite3_auto_extension() same compilation unit ruled out?

Thanks David. That works great for my immediate needs. Per below, shell.c doesn't even bother checking return code of sqlite3_create_function(). What could be simpler? --from shell.c-- static void open_db(ShellState *p, int keepAlive){ if(

Re: [sqlite] Is sqlite3_auto_extension() same compilation unit ruled out?

Have a look at the way readfile() and writefile() is implemented in the sqlite interpreter. On Tue, Jun 13, 2017 at 10:38 AM, petern wrote: > I have a situation where it would be convenient to locate externally > loadable SQLite extension code in the same

[sqlite] Is sqlite3_auto_extension() same compilation unit ruled out?

I have a situation where it would be convenient to locate externally loadable SQLite extension code in the same compilation unit as the server code. Is there a way for server main() to load those extensions located within its own compilation unit? Does the necessity of #including both sqlite3.h