By looking at these problems, I am not sure whether Perl with MySQL is a right way to go.
Do not misinterpret the above discussion as there being "problems" with Perl and MySQL. Nobody said there were problems with Perl and MySQL. The two work perfectly well together. The argument you see above is about using ORM's (e.g. DBIx::Class, Rose::DB::Object) which is an entirely separate issue which sparks arguments/debates/discussions like the one above. Start with Perl, DBI, and SQL, then maybe start looking at ORM's if you feel like it, try'em out, and use them if you feel that they're right for you.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|
