I see you haven't gotten a reply in 11 hours. I must say I know very little about
DBIx::Class, and my limited experience with MSSQL is more than 5 years ago. Anyway. I do have recent experience with
DBI (and
DBIx::Simple) and with stored procedures in Oracle.
What works for me in DBIx::Simple, using Oracle, is a call like this:
$db->query('BEGIN sp_name(?,?); END;', $param1, $param2);
(In Oracle, to call a procedure from SQL, is to put it in an anonymous block.)
So from DBI, I just treat the call to the PL/SQL block as a straightforward SQL call, with support for placeholders for the parameters. You don't have to use DBIx::Simple; in plain DBI you could use the do method, in virtually the same way.
I think you should do the same, with MSSQL: call the syntax you have to use as a straightforward SQL call, and use placeholders.
I'm quite sure DBIx::Class has ways to directly embedding SQL calls in your modules, and that's the route to take.
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.