On Wed, Jan 09, 2008 at 10:06:30PM +0000, [EMAIL PROTECTED] wrote:
> Nicolas Williams <[EMAIL PROTECTED]> wrote:
> > Would you recommend that we not make SQLite 3.x in Solaris available to
> > third parties?
> 
> I think having a libsqlite3.so available is great.  There will likely
> be smaller apps that want to compile with -lsqlite3.  I think it is
> nice to accommodate them.  Presumably, Solaris will be using sqlite3
> internally (in place of sqlite2?) so it does not cost you anything
> to make it available to third parties.

SMF will probably be the last thing to move away from SQLite 2.x (it's
been stable and performant, and SMF is such a critical early boot
component that dealing with incompatible schema or DB changes presents
serious challenges in some of the install/update/patch scenarios).

But, yes, we will use SQLite 3.x internally, as well as in bundled apps
like Firefox.

There is a cost to making something available to third parties, namely:
more work or delays in the event that the need arises for an
incompatible change.

> On the other hand, I recommend to anybody building an application
> that you should statically link against SQLite.

OK.  I'll pass this advice along.

> Regardless of whether or not you make libsqlite3.so available,
> you definitely should make the sqlite3 CLI available.  That is
> a very handy thing to have when using a shell.

Agreed!

Thanks,

Nico
-- 

-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------

Reply via email to