On Thu, 15 Jul 2004, [EMAIL PROTECTED] wrote:

> Don't forget that some users of your package may have databases being accessed
> via multiple languages, multiple applications, etc., and it may not be
> possible to upgrade the database.  Therefore, they probably need the ability
> to continue to use old databases.  That was the reason (not just because of an
> API change) that sqlite3 has the '3' appended.  It allows both 2.8.x and 3.0.x
> to be installed and usable at the same time.

You can do this in perl via installation prefixes (just install in a local 
directory) and either -I, @INC, or the "lib" pragma.

Admittedly it becomes an issue if you have something like mod_perl wanting 
two different versions.

I'm not dead set for one particular upgrade path, but I can very much see 
both sides - if I keep the name then things on CPAN that use DBD::SQLite 
will get an upgrade without any code changes (the DBD::SQLite API remains 
identical). But I'll ask on dbi-users what they think there, and I'll talk 
to Tim Bunce about it next week at The Perl Conference.

Matt.


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

Reply via email to