I can only beg the forgivness of you and other readers of my post for my late night levity sent in a moment of weakness sparked by the freak combination of St. Valentines day, my mother visiting from California and ribbing from the chatterbox for being chicken.

First off, I must confess to being a complete moron when it comes to Oracle's Java stored procedures, being as I tend to avoid being locked into one vendors world when it comes to database design. It seems to me that your question in many ways answers itself. It don't do dat.

DBI isn't a module designed for vendor specific database features. It's to give programmers an interface to standard SQL features across vendors. So, what do you do when the free stuff that people wrote doesn't do what you need it to do?

One question that I ask myself when dealing with problems that are on the edge and seem to stump people that I respect is Am I trying to hard? Is there a simpler way to do this problem? In your case it would be Do I really need a Java stored procedure?

Computers are donks Vladb. There's always a way to get them to do something. You just need to play with them and not get yourself trapped in the boxes that they like to create.

I consider you blessed Vladb. I have yet to come across a general problem that I need solved that someone else hasn't already written a module for in Perl. In fact there have been several times when I have written things only to discover that there's a module out there that already does it a hundred times better. The fact that it doesn't do what you want is your chance to shine! Your chance to step up to the plate and win one for the Gipper! (Oops... mixing baseball and football there) Get out there soldier and show em what you got. I know you can do it my boy, after all, you're a Perl Monk, damnit.

()-()
 \"/
  `

In reply to Re: Re: Re: Invoking Java stored procedures by ignatz
in thread Invoking Java stored procedures by vladb

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.