I took a look at all them as well. The two I really tried experimenting with with DBIx::Class and Rose::DB::Object. One thing I did not like about DBIx::Class was that it focused on using SQL::Abstract a bit much, and that module cannot really handle complicated SQL very well. Also SQL::Abstract has problems when your database structure has 'issues'. You can customize some parameters to try and get around it but it become a hassle and did not offer anything better than writing custom SQL did.
Another issue I encountered, is that both are dependent upon a reasonable database structure. The project I was trying to us them in, did not have one (don't ask me why I just had to work with the dam thing). For examples, tables scattered across multiple schema's and using column names which are also SQL keywords, example LEVEL is an oracle keyword.
My point is, that sometimes, your underlying structure is so bad that you cannot rely upon on the ORM modules to help you fix it. Just a warning...
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||