All tests successful.
Files=24, Tests=355, 6 wallclock secs ( 3.12 cusr + 0.91 csys = 4.03 CPU)
Woot!
Now I'm going to extend it a bit - SQLite 3.0 allows some nice things like busy handlers which I'd like to add before release.
Re:insert id
Matts on 2004-07-17T10:15:13
Err, any idea how I do that? The DBI::DBD docs don't say anything about it.Re:insert id
Juerd on 2004-07-17T11:21:27
I don't know exactly (familiar with neither C nor DBI's internals), but at least DBD::mysql and DBD::Pg implement it. grep its tree for dbd_db_last_insert_id.
See also http://groups.google.com/groups?selm=20030307221500.GQ352%40dansat.data-plan.com Re:insert id
Matts on 2004-07-18T08:57:36
Got it working. Thanks.
Maybe not today, but I know that for new projects I'll definitely choose the newer version. I'm not sure I'd want to move existing projects there due to file format issues (how did you address that, btw? or did you?).
Haven't gotten to use SQLite at work as much as I might have liked, but I've been using DBD::SQLite extensively for my master's thesis work. As I said before, I owe you a nice meal.
Re:This is going to help me
Juerd on 2004-07-17T11:29:53
I'm not sure I'd want to move existing projects there due to file format issues.
Converting an SQLite 2 database to SQLite 3 is a matter of doing: sqlite foo.db.dump | sqlite foo.db.new; mv foo.db{,.old}; mv foo.db{.new,}
