Hi everyone,
This may be a stupid question. If so please humor me with a stupid answer. However:
I FINALLY have the fun fun fun chance to change one of my data loads to use the DBI instead of the procedures I hacked together. In true ksh style I had written my loads to fire a sql script (calling a stored proc) that was stored separately. It seems to me the DBI wants the text of the sql script embedded piece by piece in the code. I have looked around for examples because even though the DBI seems straightforward, it doesn't take much to confuse me. I don't see examples of firing a sql script from the DBI (like this sqlplus /@dbname < @script.sql > logfile.log ... Gosh do I miss unix, everything was SO EASY)
So my questions to you, my learned friends, are:
1. is it not perl-style to store the sql in a separate file? I understand I may be missing the opportunity for more specific error handling here but honestly at this point it does not matter. The thing fails, I restart the whole script.
2. Does anyone have an example of firing the DBI and calling a sql script like I could so easily do in ksh?
Any and all comments are welcome. Thank you
I wish everyone a rested and relaxing weekend.
Lisa Koivu
Oracle Database Monkey
Fairfield Resorts, Inc.
5259 Coconut Creek Parkway
Ft. Lauderdale, FL, USA 33063
