Hello dbi-users,
I hope the following question is not off topic. I am new to a company that
makes intensive use of Oracle under UNIX. Most Applications are Oracle
Forms- and Oracle Reports-based. But there is also a vast variety of batch
scripts. Currently all these scripts are SQL*Plus scripts (using SQL and
PL/SQL) and shell scripts. People here do not speak perl :-(. Now I am going
to give a course on perl and DBI. So far so easy. But my main problem is to
convince developers and management to use perl/DBI on an official basis (as
substitute for or complement to SQL*Plus). So I would be very glad if you
can give me some argument for (or against [are there any? :)]) Perl/DBI
compared to SQL*Plus scripts wrapped into shell scripts. Of course I have my
own portfolio of arguments, but would be glad to hear from your experience
or ideas...
E.g. I am not sure about a performance comparison (will make some tests
though). Success stories would be a great help too.
Thanks for any comments,
Peter
P.S: Arguments I immediately see:
PRO:
1. Perl/DBI is more flexible:
a) working with file system (how easy is it in PL/SQL to read from and
write to files???)
b) lots of existing modules in perl (XML, Excel spreadsheet access, web
based applications,...)
2. Perl/DBI is a "real" language (loops etc.) compared to SQL*Plus (counter
argument: PL/SQL is a real language too, and can be used within SQL*Plus.)
3. DBI is database independent, migration to other databases is easier.
4. Anything you can do with PL/SQL can be done with perl/DBI, since you can
use PL/SQL within Perl/DBI
CONS (expected to hear):
1. We dont want to learn a new language...
2. More Oracle developers than perl/DBI developers on the market (I doubt
this is true, but I have heard this argument).
3. PL/SQL is better integrated into oracle, e.g. as far as data types are
concerned (in fact working with Oracle date values, NULL values,... seems to
me to be easier in pure PL/SQL than Perl/DBI).
