Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

vek (2312)

vek
  (email not shown publicly)

Journal of vek (2312)

Friday May 10, 2002
03:29 PM

PL/SQL - Yipes

[ #4838 ]

It's official, now that we're one programmer short I'm now going to be maintaining some of our PL/SQL code. In fact I got my first bug report ticket assigned to me this morning. The funny thing about all this is that I haven't written a single line of PL/SQL code in my life. I hope they don't expect this ticket resolved before the end of the day ;-) /me goes off to Borders to buy some PL/SQL books...


List all Journal entries
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

PL/SQL - Yipes 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • In my experience, there is nothing I could do in PL/SQL that I couldn't code faster and easier using Perl. PL/SQL is a helluva lot clunkier. Any potential speed advantage to using PL/SQL is lost when considering the load on our Oracle servers.

    Of course, you may not have the luxury of being permitted to change them to Perl code. Perhaps they are stored procedures?

    • Perhaps they are stored procedures?

      Yep, that's exactly what I'm working with. This should be quite interesting - at the very least it will be something else to add to the ol' resume/CV I suppose.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.