Yes, I took a look at it.

Your object attributes don't always coincide with your table columns. It's not always 1-1. And the pixie model may be great and all, but if you hook it up to a db, then you must care what it does for performance sake. A missing index could cause a world of trouble if pixie decided to pull back an object using the wrong method (verb, not object).

If piexie doesn't care about how your db is laid out, then see above, it may not be using indicies correctly, or not doing thins in an efficient manner, ala selecting large groups of data (multiple rows etc..).

If you haven't used pixie yourself, I'm not quite sure how you can be so confident in it, regardless of who wrote it, since the best programmers in the world can still make the strangest mistakes. You prolly won't believe me anyway, here is a document from IBM on pixie and it's drawbacks as well as its pluses.

As you see, for small projects, it prolly does wonders, but for a huge project, I doubt I would look at it all that quickly, since custom SQL is usually better than that generated by a general api.

-s


Play that funky music white boy..

In reply to Re: Re(3): Mixing Mysql and Perl by exussum0
in thread Mixing Mysql and Perl by SavannahLion

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.