I'm filing this self-review case on my own behalf. The update of SQLite3 to 3.6.17 will also enable a heretofore disabled feature: loadable extensions. Loadable extensions are shared objects that can be loaded with sqlite3_load_extension(). See:
http://sqlite.org/c3ref/enable_load_extension.html http://sqlite.org/c3ref/load_extension.html The interface stability for these is as for the rest of SQLite3 in Solaris. See PSARC/2008/120. Change history: http://sqlite.org/changes.html The only changes which have any possible interface stability impact are: - The sqlite3_create_function() family of interfaces now return SQLITE_MISUSE instead of SQLITE_ERROR when passed invalid parameter combinations. - When new tables are created using CREATE TABLE ... AS SELECT ... the datatype of the columns is the simplified SQLite datatype (TEXT, INT, REAL, NUMERIC, or BLOB) instead of a copy of the original datatype from the source table. I don't believe these are serious enough even to merit a fasttrack. The latter is a result of the fact that there isn't always a source table in a SQL SELECT statement. Nico --
