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 ]

tinman (2063)

tinman
  (email not shown publicly)

tinman spent a few years mucking around industry before going back to school for a Masters. Currently not enjoying the weather in North England..

He wrote Perl that looked suspiciously like C code in 1998, while working as an intern, and has been trying to cure that bad habit ever since.

Journal of tinman (2063)

Sunday February 01, 2004
12:52 AM

10g..! and I didn't even notice

[ #17130 ]

Oracle had released 10g (not for Win32, Linux yet) and I didn't even know.. awww..

Looking forward to trying out regular expression "where" clauses... wheeee

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.
  • by djberg96 (2603) on 2004.02.01 11:46 (#27938) Journal
    I usually start out trying a LIKE clause, and usually remove it because it hammers the database and it' *slow*. When it comes to doing *any* kind of regular expressions, more often than not I simply grab the entire string (usually a long data type) and use Perl to do my regular expressions. This simplifies the SQL, is usually faster, and keeps me under the IO limits.

    I don't expect this to be any better with 10g.