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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I agree this is bad design, but I think it springs from the subtle difference between the Oracle SQL language and the SQL*Plus program language. Oracle is a madness of interfacing between different languages: PL/SQL, SQL, and SQL*Plus are three separate languages to learn, and they all tend to embed each other. I remember having to explain about three times to a former manager why I could not run an SQL*Plus report from PL/SQL stored in the database before she finally got it.

    Strangely enough, even though I believe the SQL standard provides for ; as a statement terminator, I think that / and ; are actually processed only by SQL*Plus. I know for a fact if you pass in a ; in OCI or DBI you'll get an error because Oracle's SQL can't handle it. So, the minute SQL sees ; or / it knows that this "string" is done (the string is a string of characters which are going to be passed to the (PL/)SQL engine), and it goes back to SQL*Plus command mode, and you lose the ability to do PL/SQL comments.

    --
    J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers