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.

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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • For example, in my Test::DBIx::Class module, which is a tool to ease DBIC testing, you can specify a target database type and if you leave the connect info blank, I will try to automatically deploy a database (either mysql or postgresql) to a temporary area. If none of these are available, I fall back to SQLite. So, ideally if you are testing, I should first look for this system, and if it's not setup, fall back to sqlite? Seems like we have some overlapping concerns and might be valuable to collaborate a bit. My stuff is at http://search.cpan.org/dist/Test-DBIx-Class/ [cpan.org] and I am currently working on supporting mysql replication. Let me know what you think. At the very least I think I want to use your framework to help with the 'default' mode. john
    --
    Waiting on the Road to Eventually, I lost my Place On Line
    • (Sorry for the late answer...)

      I agree that we have overlapping concerns, and that I have probably overlooked some use cases (I was concerned with testing over as many database engines as possible).

      Regarding defaults, Test::Database will automatically fallback on any file-based database that is available.

      Test::Database is about letting the system owner do all the hard work of configuring databases for us, and just providing what's available. Test::Database only provides the DSN information, but filling the