Why not just have a PHP based wrapper that would extend SQLite3 class as SQLite2 equivalent...
On Wed, Jun 16, 2010 at 7:17 AM, Pierre Joye <pierre....@gmail.com> wrote: > On Wed, Jun 16, 2010 at 1:04 PM, Ilia Alshanetsky <i...@prohost.org> > wrote: > > 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... > > That's why I explicitly mentioned 'basic' methods (exec, query and > similar), the python bindings do it for example. It makes obviously no > sense to do it for many advanced features. SQlite3 APIs allow that > easily (cleaner naming). > > Cheers, > -- > Pierre > > @pierrejoye | http://blog.thepimp.net | http://www.libgd.org > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
