Re: [sqlite] Determine version compatibility
> - If you VACUUM a 3.3.0 - 3.3.6 database in a later sqlite version it > will change the sqlite file format to the sqlite version of the program > that issued the VACUUM, and versions 3.3.0 - 3.3.6 will not be able to > read the VACUUMed database. My mistake. The above is wrong. This should read: - If you VACUUM a 3.0.0 - 3.2.8 database with a 3.3.0 - 3.3.6 sqlite version, it will change the sqlite file format to the sqlite version of the program that issued the VACUUM, and versions 3.0.0 - 3.2.8 will not be able to read the VACUUMed database. Please correct me if I've made any other errors. Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list=396545433 - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Determine version compatibility
> 3.0.0 is compatible with 3.5.1 and everything in between. Minor caveats if you happen to use different versions of sqlite libraries accessing the same database files: - Default databases created with versions 3.3.0 through 3.3.6 cannot be read by versions of sqlite from 3.0.0 through 3.2.8 (unless the legacy file format is explicitly used). - If you VACUUM a 3.3.0 - 3.3.6 database in a later sqlite version it will change the sqlite file format to the sqlite version of the program that issued the VACUUM, and versions 3.3.0 - 3.3.6 will not be able to read the VACUUMed database. Hopefully I've remembered the correct version numbers. Need a vacation? Get great deals to amazing places on Yahoo! Travel. http://travel.yahoo.com/ - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Determine version compatibility
bizshop <[EMAIL PROTECTED]> wrote: > > So I think it is creating databases in 3.3.7 - is that incompatible with > 3.3.5? > Except for corner cases (such as using language feature from one version of SQLite that did not exist in a different version) all versions of SQLite that being with "3" are compatible. That means 3.0.0 is compatible with 3.5.1 and everything in between. We take backwards compatibility very seriously. But 3.x.x is not compatible with 2.8.17. -- D. Richard Hipp <[EMAIL PROTECTED]> - To unsubscribe, send email to [EMAIL PROTECTED] -
[sqlite] Determine version compatibility
I am trying to use PHP and SQLite on N800 Nokia Internet Tablet - a great handheld Linux based computer, but not exactly Linux (uses Maemo). That means compiling is not an option for me, and most Linux things are 'ported' over. I can create a new database and insert from both command line and using php pdo in the NGINX web server (localhost in browser), but in browser can't access database created from commandline, and in commandline can't access database created from browser/localhost. Both say "Encrypted or is not a database" Is there a way to get the version info from within PHP_PDO? And are my versions incompatible? Anyway, I installed SQLite and from command line it shows SQLite version 3.3.5 That one is easy. When running NGINX web server as localhost and doing phpinfo() I get (0nly applicable parts shown): Configure command shows -with sqlite PDO Drivers sqlite2, sqlite in the pdo_sqlite section: PDO Driver for SQLite 3.x enabled PECL Module version (bundled) 1.0.1 $id:pdo_sqlite.c, v1.10.2.6.2.1. 2007/01/01 sebastion Exp $ SQLite LIbrary 3.3.7 But then in the SQLite section SQLite support enabled PECL Module version 2.0-dev $id: sqlite.c, v 1.166.2.13.2.6 2007/01/01 sebastian Exp $ SQLite Library 2.8.17 SQLite Encoding iso8859 So I think it is creating databases in 3.3.7 - is that incompatible with 3.3.5? -- View this message in context: http://www.nabble.com/Determine-version-compatibility-tf4576460.html#a13063321 Sent from the SQLite mailing list archive at Nabble.com. - To unsubscribe, send email to [EMAIL PROTECTED] -
