Hi,
While working on a large embedded project using PHP and SQLite, I ran
into some compatibility issues where the sqlite guys broke file
compatibility on a dot release.
The SQLite situation is:
- SQLite 3.3.x can read and write any SQLite 3.x file
- SQLite 3.2.x cannot work with SQLite 3.3.0+ files, as they broke
compatibility between 3.2.8 and 3.3.0 - Of course, SQLite 2.x is incompatible with 3.x
The PHP situation is:
- the sqlite extension is used for Sqlite 2.x (that's fine)
- PDO's sqlite driver uses SQLite 3.2.8
This begs the question on should the PDO driver be upgraded to 3.3.x or
not, and what is the strategy for backwards compatibility. Certainly,
upgrades will be straight forward as apps written today will have a
backwards compatible sqlite. However downgrades (moving from sqlite
3.3.x to 3.2.x) will not work.
Are there any plans for upgrading the SQLite driver?
On a side topic: I noticed the Fedora Core 5 developers are trying to
package a PHP5.1+ RPM with an external sqlite RPM dependency. This
doesn't appear to make any sense as their sqlite RPM is 3.3, and
upgrading the sqlite3 driver in PDO doesn't appear to be as easy as
replacing the sqlite directory under the driver, and there doesn't
appear to be anyway to compile the driver against an existing sqlite
installation (e.g. --with-pdo-sqlite=[DIR]).
Will the PDO driver builds be updated to support this type of build
configuration?
Thanks,
Al
Are there any plans for upgrading the SQLite driver?
Yes. We didn't want to do this in a point release of PHP because of
BC concerns.
there doesn't
appear to be anyway to compile the driver against an existing sqlite
installation (e.g. --with-pdo-sqlite=[DIR]).
This should work. I believe this was broken for a while, but has
recently been fixed in CVS.
--Wez.
Are there any plans for upgrading the SQLite driver?
Yes. We didn't want to do this in a point release of PHP because of
BC concerns.
I think moving to 3.3 would be more favorable to BC, as 3.3 can work
with 3.2 sqlite files, but 3.2 cannot work with 3.3 files.
Al
Yes... but since we only create the older format of sqlite files with
the bits we bundle with PHP, preserving compat with our own stuff is
higher priority.
If you're interoperating with other processes that create sqlite
files, then you should probably be building against your own install
of libsqlite.
We're going to look at upgrading the library for PHP 5.2, and not before then.
--Wez.
Are there any plans for upgrading the SQLite driver?
Yes. We didn't want to do this in a point release of PHP because of
BC concerns.I think moving to 3.3 would be more favorable to BC, as 3.3 can work
with 3.2 sqlite files, but 3.2 cannot work with 3.3 files.Al