The specific way of handling dynamic sql via stored procedures varies depending upon what flavor of sql you are using, but they boil down to eval'ing statments inside of the procedures or if-else blocks. Be forewarned, though, that eval'ing inside of stored procedures causes a performance hit.

To get the most optimal performance, though, it would be best to eliminate the dynamism, if you can do so w/o creating a mess. If your dynamic cases really boil down to a manageable set of statments, then it would probably be best to write/generate separate procs for each!

If, for example, the following Perl/SQL stement:

my $statment = "SELECT COL_1, COL_2 FROM $table";

is really only ever going to give you three SQL statments:

SELECT COL_1, COL_2 FROM TABLE_1 SELECT COL_1, COL_2 FROM TABLE_2 SELECT COL_1, COL_2 FROM TABLE_3
then you may be better off creating three procs (pseudo-SQL follows):

CREATE PROC get_stuff_table1 AS SELECT COL_1, COL2 FROM TABLE1; CREATE PROC get_stuff_table2 AS SELECT COL_1, COL2 FROM TABLE2; CREATE PROC get_stuff_table3 AS SELECT COL_1, COL2 FROM TABLE3;

This can get really out of control, though, if you are going to end up many procs. If you are going to end up with more than a handfult then you should consider generating them. Of course, this process can be eased if you generate your procs with a nice language such as, oh... umm.. Perl.

Hanlon's Razor - "Never attribute to malice that which can be adequately explained by stupidity"

In reply to Re: Re: Re: Navigating the plethora of SQL modules by Art_XIV
in thread Navigating the plethora of SQL modules by dragonchild

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.