I like where you are headed.

The basic problem which this addresses is Moose classes and database schemas getting out of sync.

Unfortunately, it assumes that the database schema is always right, which is not necessarily true.

I think the ideal solution is to make a Role that optionally injects attributes, or compares attributes and schema.

I see the problem that in a group, sometimes people make changes to code and database, and there is no easy way to check whether the ORM mapping is valid.

I had planned to do something with SQL::Translator to handle this, by making a Parser that can parse Moose class hierarchies. (To be honest, s/I had planned/It sure would be nice to have/g)

In reply to Re^4: Moose + ORM by Anonymous Monk
in thread Moose + ORM by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.