Thanks :-) Do you have any suggestions regarding what you'd like the module to support? As I wrote I plan to add support for stored procedures in mysql, but I have neither Oracle nor PostgreSQL and do not need to support them myself. Another thing I consider adding is the ability to write the generated methods to the disk (or maybe some other cache as well?) and load them from there by the next instance of the script, though I'm not sure how big improvement would that be. And possibly some way to have all the methods generated right away instead of on the first use and optionally written somewhere. That way you might be able to generate all the code and later use the generated code directly instead of this module.

Even as it is you can use the module to generate the method and copy&paste it somewhere. If you set the environment variable DBIx_Declare_Debug (before the first use DBIx::Declare ... in your script) you get some debug info and the generated code or if you set the $db->{_show_generated_code} to a true value, you get just the generated code on STDOUT.

Jenda
Enoch was right!
Enjoy the last years of Rome.

In reply to Re^2: RFC: DBIx::Declare - generate code to call stored procs/SQL statements by Jenda
in thread RFC: DBIx::Declare - generate code to call stored procs/SQL statements by Jenda

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.