Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • That sounds like a probably reason. SQLite 2.x and 3.x are not compatible qua databasefile.

    I don't know what version of SQLite PHP 5 is using, but checking for Perl is quite easy, according to the changes file [], DBD::SQLite started using SQLite 3 starting with DBD::SQLite version 1.00. So, whatever version it is you have, try installing the latest one of the other generation.

    I wish Perl had a better way to have different generations of modules live together, but I think the best you can do in order not to

    • And thus the reason for DBD::SQLite2 []. From the README for DBD::SQLite2,

      Note: DBD::SQLite2 is the old version of DBD::SQLite, and embeds version 2.x.x of the sqlite library. The current version of DBD::SQLite embeds version 3 (or possibly later if I forget to update this file). This release is designed to allow you to have both versions installed on the same system.
      • The SQLite 3.0 thread just occured on php-internals. It'll happen, but not before ApacheCon. :)

        • cool.

          while this is neither a php nor perl concern, I was able to put my finger on why this all felt so strange to me this week at nyphp: if versions 2 and 3 databases are not compatible, I would expect that a version 2 client would bomb, however I would expect a version 3 client to say "whoa - you're using a version 2 database." the way it is now, you get this cryptic "file is encrypted" error in both directions, which is very user unfriendly.