On Fri, Aug 30, 2013 at 9:11 AM, John McKown <john.archie.mck...@gmail.com>wrote:
> I know that sqlite is designed as an "embedded" SQL engine. But I am > curious if there is a specific reason to _not_ have a DLL/shared object. > The main reason I ask is that a DLL is required in order to create a sqlite > Java JDBC interface. > SQLite works either way. The reason to prefer static linking is because then you, the application developer, are in control of what version of SQLite you are using, rather than being at the mercy of a system admin, who might supply you with an older version of SQLite that lacks features you want. http://www.sqlite.org/mark/queryplanner-ng.html?applies+equally&This+is*control#mark We commonly get calls here at the office from Windows users who are using some application that wants to use SQLite in WAL mode (available only in SQLite 3.7.0 and later) but have a 3.6.x DLL installed on their system. All such grief is easily avoided by statically linking. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
