I am pleased to announce that DBD::SQLite (Self Contained RDBMS in a DBI Driver)
version 1.24_01 has been released on CPAN (by Adam Kennedy).
The main feature of this release is that now DBD::SQLite also uses amalgamated
source recommended at sqlite.org, meaning that the entire C source code of the
SQLite library itself is now contained in a single file rather than being spread
over several dozen files. Some advantages of this change include better
performance due to cross-file optimization, and also an easier compilation on
platforms with more limited make systems.
The last DBD::SQLite release that doesn't use the amalgamated source is version
1.23, which was released 2 days earlier.
Also the bundled SQLite library with both 1.23 and 1.24_01 has been updated to
v3.6.13 from v3.6.12 that 1.20 had.
Further improvements in 1.24_01 over 1.20 involve mainly a significant
modernization of the whole test suite, so it uses Test::More, and also there
were more bugs fixed, minor enhancements made, and RT items addressed.
See http://cpansearch.perl.org/src/ADAMK/DBD-SQLite-1.24_01/Changes as well as
http://sqlite.org/changes.html for details.
Given that the switch to amalgamated SQLite sources is arguably a very large
change (or arguably a very small change), mainly in subtle ways that might
affect build/compile systems (though actual SQLite semantics should be
Please bash the hell out of the latest DBD::SQLite and report any outstanding
bugs on RT. Test your dependent or compatible projects with it, which includes
any DBMS-wrapping or object persistence modules, and applications.
If you want in to DBD::SQLite development, then join the following email/IRC
forums which MST created (the mailing list, I am administrating):
#dbd-sqlite on irc.perl.org
And the canonical version control is at:
Patches welcome. Ideas welcome. Testing welcome. Whining to /dev/null.
Note that today's switch to amalgamated sources is the last major short term
change to DBD::SQLite that I personally expected would happen (sans updates to
the bundled SQLite library itself), but other developers probably have their own
ideas for what directions the development will go next.
Please do not reply to me directly with your responses. Instead send them to
the forums or file with RT as is appropriate.
Thank you. -- Darren Duncan