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'm a reluctant lover of PL/SQL. I have an orange O'Reilly Oracle shelf sitting in front of me that's about two and a half feet wide. At one time, I'd read about a third of these all the way through and had plans to finish the rest, but then I needed less Oracle, and now in my new job I currently don't need it at all. (But with this prominent shelf, when we do need Oracle, they'll know which employee to go to. :) )

    I felt a deep, visceral agreement when you said "Instinctively, I found the idea of a cus

    --
    J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
    • My original database experience order was MySQL -> Oracle -> Postgres.

      Once I discovered Oracle, I realised how dodgy MySQL truly was, and Postgres for me has always been a less corporatey, less thorough, but slightly more sane version of Oracle.

      I do like that you can relatively cleanly mix SQL syntax with the Ada-like coding in Oracle PL/SQL. The parsing implications (how complex their parser must be to deal with it) are amazing.

      I see where Microsoft copied their idea from for doing the same in C#.

      Once I get a bit more familiar with Oracle PL/SQL, I do plan to looking in more detail at how Postgres has taken the idea and run with it.