Pierre, If they are using PDO there are no issue, but when it comes to the extension the Sqlite3 interface is more similar to PDO in naming conventions and offers only OO interface. The SQLite2 offers both OO and procedural interface and follows its own naming convention. I don't think we should be added boat-load of wrappers for SQLite3 extension...
On Tue, Jun 15, 2010 at 2:18 PM, Pierre Joye <pierre....@gmail.com> wrote: > hi Ilia, > > On Tue, Jun 15, 2010 at 1:41 PM, Ilia Alshanetsky <i...@prohost.org> > wrote: > > After speaking to a few developers in DPC, I think it makes sense for us > to > > drop the Sqlite2 extensions from Trunk as they are superseded by the > Sqlite3 > > extensions. The sqlite2 library is no longer maintainer and the migration > > path from version 2 to 3 is very simple. Unless there any objections, I'd > > like to make this happen in the next week or two. > > > No objection here. > > However I would like to have the set of basic methods (not version > specific, exec, open, etc.) to remain the same across versions so the > migration could be as simple as using the new name of the sqlite > class. > > Cheers, > -- > Pierre > > @pierrejoye | http://blog.thepimp.net | http://www.libgd.org >
