It seems to me that there are several different arguments going on here and one that has nothing to do with Stored procedures is:
Should there be SQL mixed with perl
This question has nothing to do with the stored procedure question. If you are using code like
my $sql = "EXEC dynamic_example @firstname = ?";
$dbh->execute('chris%')
to get SQL out of your perl code, then I whould suggest that you should use
code like
$dbp->execute('dynamic_example', firstname => 'chris');
where $dbp holds an object that can either use ad-hoc SQL or stored procedures.
The advantages to this approach are that interface to the database is a
single object and all the procedures or sql that is accessing the
database are well known. The main disadvantage is that if the database
needs to accesed in a new way the $dpb object must be extended. And if Stored procedures are used, then the database has to be extended as well.
-- gam3
A picture is worth a thousand words, but takes 200K.
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.