Re: [sqlite] PHP5 && SQLite3
| From: | Derrell dot Lipman at UnwiredUniverse dot com | Date: | Wed, 20 Oct 2004 02:01:59 +0000 |
| Subject: | Re: [sqlite] PHP5 && SQLite3 | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-13411@lists.php.net to get a copy of this message | ||
FYI, attached is a highly edited (for brevity) series of responses to the
SQLite mailing list, to a query about SQLite3 being included in PHP 5. My
reply is first.
D. Richard Hipp is the author of SQLite, so his response is of particular
relevance...
Derrell.Lipman@UnwiredUniverse.com writes:
> "julien" <j.griffon@eurelis.com> writes:
>
>> does anyone know if PHP will integrate SQLite3 per default in version 5.1 ?
>> Actually PHP 5.0.2 include only SQLite2.
>
> The plan _is_ to integrate SQLite3. There are two of us who may integrate
> it, depending on availability and need. There's no schedule for when it
> will be completed, but it is reasonably high on some of our priority lists.
>
> Derrell
"julien" <j.griffon@eurelis.com> writes:
> thank you for your answer. I put this question because compatibility between
> SQLite2 and SQLite3 seems poor. So i do not wish to begin development with
> SQLite2 i prefere to continue with Mysql while waiting (I done some bench
> ant will choose sqlite in the futur and migrate this application). Moreover
> recompile PHP5.0.2 with SQLite3 (under windows platform ...) is too
> difficult and is impossible on my production web server. So i'm very
> impatient :))
>
>
> (sorry for my very poor english)
"D. Richard Hipp" <drh@hwaci.com> writes:
> julien wrote:
>> I put this question because compatibility between SQLite2 and SQLite3 seems
>> poor.
>
> Poor? More like non-existent. SQLite2 and SQLite3 have a very similar
> design but both the interface and the underlying file format are quite
> different and imcompatible.
>
> ...
>
> SQLite3 is designed so that it can be statically linked into the same
> executable as SQLite2. One plan for PHP might be to link in both libraries.
> When opening an existing database, check the header and use either the
> SQLite2 or the SQLite3 library depending on what kind of database it is.
> Create new databases as SQLite3. The scripting interface would be the
> same and the user would never know the difference. In this way, you
> preserve backwards compatibility with existing SQLite2 database files
> while at the same time taking advantage of new SQLite3 features.