Re: :) What you can't do in java you can do in perl
- From: Wolfgang Breitling <breitliw@xxxxxxxxxxxxx>
- To: "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 29 Sep 2004 07:37:26 -0700
I am no expert in either Java or Perl, far from it. But then I'm not a
developer. However I use Perl quite a bit to do file manipulation such as
process trace files. There it is just faster than Java, both in terms of
development time but also in execution time. It runs rings around Java - and
most anything else.
The same goes for repetitive database monitoring tasks. I do those either as
PL/SQL database jobs or Perl scripts which have the repetition internal to
avoid frequent connects to the database.
There is one task where I invested some time to develop a Java class because
Perl let me down and that is to extract the "dbms_stats.set_xxx_stats" commands
from an export file. Those records contain length fields and invariably one of
those length fields is interpreted by Perl as end-of-file and it stops. If
someone knows how to work around that in Perl I'll gladly ditch the Java class -
it also still has a problem where it sometimes gets confused by those length
fields. But I am not using it that often that it has been worth my time to go
back and debug it, or even so desperate to try my hand at C.
Quoting Juan Carlos Reyes Pacheco <jreyes@xxxxxxxxxxxxxxxx>:
>
> What you can do in perl, you can't do in java.?
> Or why to use perl if you are an expert in java (I'm not but I'll have to be
> if I want to keep my job)?
>
>
> Juan Carlos Reyes Pacheco
> OCP
> --
> //www.freelists.org/webpage/oracle-l
>
--
regards
Wolfgang Breitling
Oracle 7,8,8i,9i OCP DBA
Centrex Consulting Corporation
www.centrexcc.com
--
//www.freelists.org/webpage/oracle-l
Other related posts:
