On Thu, 15 Jul 2004, Randy J. Ray wrote: > > (now I just have to work out a release/migration strategy - since a raw > > CPAN install will break people's apps). > > I would suggest renaming it to DBD::SQLite3, since the underlying library > itself looks to be embedding "3" into most (if not all) API hooks anyway.
I don't think I'm going to do that. The C function names have changed because their prototypes have changed. There's no real reason to change the module name except for the upgrade issue. > Are there any plans to have the option of using an already-installed SQLite, > rather than building one in-place? Besides the redundancy, there are also > issues where the lib itself is released with bugfixes but the DBD driver is > still using an older version. I'll always ship getsqlite.pl which will allow users to upgrade. And I'll gladly accept a patch which makes it optional if it finds an installed sqlite, but I won't make it the default, and I don't have any need for it myself so I won't personally be working on it. Matt. ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
