http://www.sqlite.org/loadext.html states that:
...omitting the second argument for the load_extension() SQL
interface - and the extension loader logic will attempt to
figure out the entry point on its own. It will first try the
generic extension name "sqlite3_extens
http://www.sqlite.org/loadext.html states that:
...omitting the second argument for the load_extension() SQL
interface - and the extension loader logic will attempt to
figure out the entry point on its own. It will first try the
generic extension name "sqlite3_extens
On Thu, Aug 29, 2013 at 3:53 AM, Pepijn Van Eeckhoudt <
pep...@vaneeckhoudt.net> wrote:
> http://www.sqlite.org/loadext.html states that:
> ...omitting the second argument for the load_extension() SQL
> interface - and the extension loader logic will attempt to
> figure out
On vr, 2013-08-30 at 09:09 -0400, Richard Hipp wrote:
> On Thu, Aug 29, 2013 at 3:53 AM, Pepijn Van Eeckhoudt <
> pep...@vaneeckhoudt.net> wrote:
> Recently the extension loader was enhanced (I think for 3.7.17) so that it
> tries the first naming schema first, then if that fails it tries
> sqlite3
On Fri, Aug 30, 2013 at 9:42 AM, Pepijn Van Eeckhoudt <
pep...@vaneeckhoudt.net> wrote:
> So for new development sqlite3_X_init is preferred over
> sqlite3_extension_init?
>
That's my preference.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mai
On Fri, Aug 30, 2013 at 10:37:47AM +0200, Pepijn Van Eeckhoudt scratched on the
wall:
> http://www.sqlite.org/loadext.html states that:
> ...omitting the second argument for the load_extension() SQL
> interface - and the extension loader logic will attempt to
> figure out t
On Fri, Aug 30, 2013 at 5:53 PM, Jay A. Kreibich wrote:
> be built into an SO/DLL/DYLIB and loaded dynamically, or use the same
> code to build the module statically directly into an SQLite
> library. ...*if* you use a custom entry point.
A related advantage: a custom entrypoint allows o
7 matches
Mail list logo
