[Dbix-class] DBIC usage smoke/sanity check

Bill Moseley moseley at hank.org
Tue Dec 18 21:59:51 GMT 2012


On Tue, Dec 18, 2012 at 12:20 AM, Peter Rabbitson <rabbit+dbic at rabbit.us>wr=
ote:

> 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 ki=
nd
> > 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.
>

Our sources were created by hand, so I doubt the dump would match.    But,
maybe that's a good reason to update our sources.   We have been pretty
lazy and not defining that many attributes on our columns.


-- =

Bill Moseley
moseley at hank.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.scsys.co.uk/pipermail/dbix-class/attachments/20121218/9d9=
3656d/attachment.htm


More information about the DBIx-Class mailing list