Re: [sqlite] tclsqlite3 db function exports not visible on other connections. Why not?

You wouldn't happen to have a TCL script you can share which approximates the SQLite interactive shell multiline input and .exit command to return to tclsh? Dot exit would be the only mandatory dot command needed. On Sun, Mar 19, 2017 at 12:28 PM, Richard Hipp wrote: > On

Re: [sqlite] tclsqlite3 db function exports not visible on other connections. Why not?

On 3/19/17, petern wrote: > > In fact, according to the title of that presentation, SQLite is the most > popular TCL extension in the world! > > Furthermore, if the TCL byte code engine is already linked to the SQLite > binary, one would think user defined TCL byte

Re: [sqlite] tclsqlite3 db function exports not visible on other connections. Why not?

Yes. I am aware of https://www.sqlite.org/loadext.html And that's a good point. However, one might be under the impression that SQLite is a TCL extension from DRH's presentation here:

Re: [sqlite] tclsqlite3 db function exports not visible on other connections. Why not?

You can use sqlite3_auto_extension for this. On 19 March 2017 at 11:35, R Smith wrote: > > On 2017/03/19 11:05 AM, petern wrote: >> >> Taking DRH's remarks about learning tclsqlite for the efficient coding to >> heart, I discovered a big problem. >> >> Here is the simplest

Re: [sqlite] tclsqlite3 db function exports not visible on other connections. Why not?

On 2017/03/19 11:05 AM, petern wrote: Taking DRH's remarks about learning tclsqlite for the efficient coding to heart, I discovered a big problem. Here is the simplest example from the docs and DRH presentation: TCLSH % db function myhex {format 0x%X}; % db eval {select myhex(10);} x {parray