use Perl

• Incompatible? (Score:2)

  by 2shortplanks (968)

  Won't this break all the aplications that install DBD::SQLite off of cpan and expect it to be able to read a version 2 database?
  • Re:Incompatible? (Score:2)

    by yudel (1014)

    Yup! I just upgraded from .27 to 1.0, hoping to solve a sqllite/Moveable Type bug, and.... well, I'm glad I exported my postings first! Question: Are there any utilities for converting version 1 dbs?
    • Re:Incompatible? (Score:2)

      by 2shortplanks (968)

      This document [sqlite.org] on the sqlite website that was linked to in a previous journal entry seems to suggest:

      sqlite OLD.DB .dump | sqlite3 NEW.DB
      • Re:Incompatible? (Score:2)

        by yudel (1014)

        Isn't the point of sqlite the fact that it's embedded? Because I don't seem to have any sqlite command line on my server. (I am, of course, now in the process of installing one).
      • Re:Incompatible? (Score:2)

        by yudel (1014)

        OK, it's not that hard. Here's a few more of the steps on a linux machine:
        
        go to sqlite.org and download sqlite v.3 from
        
        http://www.sqlite.org/download.html
        
        Download version 2 as well
        
        gunzip sqlite*.gz
        
        copy sqlite3-3.0.3.bin to /usr/bin as sqlite3
        
        copy sqlite-2.8.15.bin to /usr/bin as sqlite
        
        chmod 755 sql*
        
        Then, with the two different programs properly named, the command above works quite well:
        
                  sqlite OLD.DB .dump | sqlite3 NEW.DB
  • Re:Incompatible? (Score:2)

    by Matts (1087)

    That's why there are big warnings when you run Makefile.PL if you have <1.0 installed.
    
    There's little else I can do without investing a HUGE amount of time into it, and nobody is paying me to do that :-)
    • Re:Incompatible? (Score:2)

      by yudel (1014)

      Yup, I saw the warnings. That's why I made sure to export my databases so it wasn't a total disaster :-) Since the translation to the new format is relatively simple (now that I've figured it out), maybe a web page with simple upgrade instructions and more detailed warnings could be set up? Something along the lines of CAUTION: Upgrading will make previous databases unreadable without manulal intervention. See http://sqlite.perl.org for details. I'll volunteer to write a draft of the web page if you thi
    • Re:Incompatible? (Score:2)

      by yudel (1014)

      Oops! Bad formatting. I meant to say this:
      
      Yup, I saw the warnings. That's why I made sure to export my databases so it wasn't a total disaster :-)
      
      Since the translation to the new format is relatively simple (now that I've figured it out), maybe a web page with simple upgrade instructions and more detailed warnings could be set up? Something along the lines of
      
      CAUTION: Upgrading will make previous databases unreadable without manulal intervention. See http://sqlite.perl.org for details.
      
      I'll volunteer to
• This may be a bug.... (Score:2)

  by yudel (1014)

  Running MT 2.66 with DBI::SQLite 1.0 screws the dates all up.
  
  This is true whether I create a new database or upgrade from an old database.
  
  Take a look at http://www.demsformars.com/ and you'll see some truly amazing dates.
  • Updated URL. (Score:2)

    by yudel (1014)

    http://www.demsformars.com/index-bug.html [demsformars.com]

    (I'm rebuilding the main site)
    • Re:Updated URL. (Score:2)

      by Matts (1087)

      Awesome :-)
      
      I can't really help without seeing SQL.