[Dbix-class] DBIC usage smoke/sanity check
rabbit+dbic at rabbit.us
Tue Dec 18 08:20:40 GMT 2012
On Sat, Dec 15, 2012 at 10:05:07AM -0800, Bill Moseley wrote:
> I've been asked to add something to our build process that does some kind
> of sanity check on the database. For example, make sure all columns
> defined in the result class exist in the target database.
> I realize this won't catch every potential problem, but should catch
> missing columns (or tables) which is our biggest risk.
> This seems like a reasonable way to do this?
I personally would opt for an in-memory DBIC::Schema::Loader dump, and
then running comparisons between the corresponding resultsource instances.
A little bit more work- but much more robust.
More information about the DBIx-Class