in reply to writing DBI applications offline

The canonical answers are DBD::Mock (for a more purist solution) and DBD::SQLite (for a more practical solution). DBIx::Class (the current "premier Perl ORM", whatever that means) uses DBD::SQLite for all of its testing needs. This means you have a huge corpus of prior art to work from.

Note: DBD::SQLite implements a subset of ANSI SQL. This means that you will not be able to test things like triggers, views, stored procedures, etc. Nor will you be able to test usage of DBMS-specific functions or keywords (such as LIMIT, CONNECT BY, etc). For that, you will need to use DBD::Mock.

My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

Replies are listed 'Best First'.
Re^2: writing DBI applications offline
by SilasTheMonk (Chaplain) on Oct 07, 2008 at 19:16 UTC

    It seems Silas The Monk knocked over a few more umbrella stands as he bumbled around the monastery.

    First of during the installation process for mysql, the process somehow got cancelled just as it was going into the wizard part. After that nothing I tried made the wizard reappear.

    However I am mightily pleased with DBI::SQLite. Thanks everyone.

[reply]

In Section Seekers of Perl Wisdom