Stories
Slash Boxes
Comments

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

use Perl

All the Perl that's Practical to Extract and Report

SQLite to MySQL More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

numbers (Score:2)

by gav (2710)

If it's a number, treat it like one:
cmp_ok($column_value, '==', 42, 'is 42')
- Re:numbers (Score:1)
  
  by jplindstrom (594)
  
  Yeah, that's what I should have done from the beginning... :/
SQLite 3 (Score:2)

by Matts (1087)

SQLite 3 should help this (a lot!) as it only aquires an exclusive lock to actually write the transaction (i.e. during a COMMIT), everything else is mostly shared locks.

Though having gone through the conversion I suspect you don't want to go back again :-)
- Re:SQLite 3 (Score:1)
  
  by jplindstrom (594)
  
  Oh, that's not a probelem at all. I haven't moved the db config to a config file yet, but everything works with both SQLite and MySQL with the change of three lines of code.
  
  I don't do anything fancy SQL-wise and Class::DBI doesn't either. Actually, there is no explicit SQL code at all in the application. Class::DBI is niiice.
  
  There is the overhead of maintaining two dialects of DDL, but that's not a problem at the moment.

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.