Actually PL/SQL and perl can complement each other...

With a stored procedure, you can abstract your API more efficienty in some situations. For instance, you could create a stored procedure called 'add_customer' or 'ship_order', supply it with all the necessary arguments, and have the stored procedure take care of validating the arguments and inserting and updating all the proper tables (assuming that there's more than one table involved in such a transaction, of course you can develop a perl module to do your 'add_customer' subroutines, etc). And since stored procedures are executed on the database server, there is a lot less network traffic or traffic between the app and the database server. With a two-tiered approach, there's a potential to more easily develop the app on other platforms, where (gasp) perl might not be available, or you just need a different interface.

Downsides: stored procedures are usually not portable between database vendors; you're now developing one app in more than one language, so you need both skillsets available.


In reply to Re: plsql vs. perl vs. neither and API's (code) by runrig
in thread plsql vs. perl vs. neither and API's (code) by deprecated

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.