This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
sqlite3 [2008/02/08 18:49] – external edit 127.0.0.1 | sqlite3 [2008/12/03 06:04] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
===== SQLite Version 3.xx ===== | ===== SQLite Version 3.xx ===== | ||
- | **Note:** The information presented on this page does **not** apply to POPFile users on the Windows platform who installed POPFile using the installer package. The installer sees to it that the version of SQLite included with POPFile is compatible with POPFile and installs the needed libraries in such a manner that they will not impact any other software on your system. | + | **Now POPFile is compatible with SQLite 3.x!** |
===== Quick Summary ===== | ===== Quick Summary ===== | ||
- | ** DBD:: | + | You can choose either version of DBD:: |
- | ** DBD::SQLite 0.32 - 0.33 ** needs to be installed **with** modification: | + | * ** DBD:: |
- | Change Bayes_dbconnect from: | + | * ** DBD:: |
- | dbi: | + | |
- | to: | + | |
- | dbi: | + | |
- | (also if you tried a v1.X and have a Sqlite3 db which must be converted). | + | |
- | + | ||
- | ** DBD::SQLite 1.x ** Does not work without modification | + | |
+ | **Note:** POPFile v1.1.0 or later uses DBD::SQLite 1.x (SQLite3) by default. If both DBD:: | ||
+ | **Note:** SQLite3 databases are not compatible with SQLite2 databases. After POPFile converts the database, you cannot use the converted database with older version (v1.0.1 or before) of POPFile. When converting the database POPFile backups the old database to ' | ||
==== Background ==== | ==== Background ==== | ||
Line 29: | Line 26: | ||
* **CPAN** - Several updated versions were released to CPAN; | * **CPAN** - Several updated versions were released to CPAN; | ||
- | * DBD:: | + | * DBD:: |
- | * DBD::SQLite 1.00 - 1.06 - These versions are compatible with SQLite 3, but are not currently compatible | + | * DBD::SQLite 1.00 - 1.14 - These versions are compatible with SQLite 3 (and with the current |
- | * **PPM** - A release was made to the Activestate | + | * **PPM** - Several updated version were released |
- | * DBD::SQLite 1.00 - This version is **not** the same as the CPAN version with the same version number. | + | * DBD:: |
+ | * DBD::SQLite 1.13 - This version is compatible with SQLite 3 (and with the current | ||
To check on the version of DBD::SQLite installed on your machine, use the following Perl one-liner. | To check on the version of DBD::SQLite installed on your machine, use the following Perl one-liner. | ||
< | < | ||
- | |||
- | ==== Implications ==== | ||
- | |||
- | With the break in database file compatibility and version confusion, | ||
- | |||
- | * When you upgrade any existing DBD::SQLite module from CPAN, it will upgrade to SQLite version 3 , which will then require you to convert **all** SQLite 2 databases on your machine to version 3. | ||
- | * POPFile is not currently compatible with SQLite version 3 due to issues with DBD::SQLite 1.00 - 1.06. It is anticipated that those issues will be resolved for a later release of POPFile. | ||
- | * In order to have both SQLite version 2 and SQLite version 3 databases in a Perl environment, | ||
- | |||
- | ==== Recommendation ==== | ||
- | |||
- | Until the POPFile developers resolve the incompatibility issues with SQLite3, we do not recommend any POPFile users use SQLite 3 for POPFile. | ||
- | |||
- | If you must upgrade your Perl SQLite to version 3 due to other applications on your machine, we recommend you install DBD:: | ||
- | |||
- | Change bayes_dbconnect from: | ||
- | < | ||
- | to: | ||
- | < | ||
- | |||
- | Note that POPFile must be shutdown and restarted for the change to go into effect. | ||
- | |||
- | ==== The Future ==== | ||
- | |||
- | Once the dust settles and the POPFile developers have had the opportunity to fully test SQLite 3 with POPFile, we will make an orderly transition to the newer version and take care of converting your POPFile database at that time. | ||
Should you find anything in the documentation that is incomplete, unclear, outdated or just plain wrong, please let us know and leave a note in the Documentation Forum.