One of the differences between the various modules is how they store the SQL.
SQL::Catalog stores the SQL in an RDBMS;
DBIx:POS stores it in Plain Old SQL, a POD-like format;
Class::Phrasebook::SQL stores it in XML.
Personally I have a preference for storing the SQL in plain text files for easy editing. I use SQL comments to name the snippets and read the names and snippets into a hash with a simple parse on /;\n\n+/. One advantage of doing it that way is that the files are nothing but pure SQL and so can be run through dbish or other SQL-file processors specific to various RDBMSs and can be easily read by DBAs with no knowledge of how the SQL is used in an application or even what language the app is written in.
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.