I'm very green at OO perl, so I can't address the main topic . I would like to provide some perspective from the DBA side.
In an OLTP database, stored procedures, and triggers have to be very carefully done, or they can cause more performance problems than they solve. SP's and triggers can also cause a lot of headaches when the database is being replicated.
As DBA,I ask my perl folks to optimize their SQL and tell me the end requirement for delivery of the info. I'll opt tune indexes if needed and load balance large
batch jobs to minimize impact on response time.
We now return you to princepawn's original topic...
Dave
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.