Anthony,
I encountered the exact same problem as you described when I upgraded my
perl installation from 5.004_04 to 5.6.1 quite a while ago. Scripts that
used both DB_File to access berkeley DB files, and DBI to access oracle
caused the DB files to become corrupted whenever they were modified.
Bob,
> All works fine in batch mode from a command console (eg, c:\mysql\bin\mysql
> < CommandFile ). Also works fine as 'mysql> source CommandFile'. But there
> must be a way to do this thru the DBI API. I've tried the obviuos $dbh->do(
> "source PerlScript" ) and everything else I can think of.
Eric,
Then you are still in luck. PostgreSQL comes with a comparable feature to
oracle's PL/SQL, called PL/pgSQL. You can read about the details here:
http://www.postgresql.org/idocs/index.php?plpgsql.html
chris
On Mon, 30 Jul 2001, Eric, Audet wrote:
> Oh ... my database is PostgreSQL (ope
Philip,
I just scanned through the docs for DBD::Xbase and noticed the last
sentence of the description states:
The DBD::XBase doesn't make use of index files at the moment. If you
really need indexed access, check XBase(3) for notes about support for
variour index types.
If its possible in you
Phillip,
Probably the best solution would be to create an index on your table, and
use a where clause in your query to restrict the results you return to
just the ones that need to be processed in the current operation. Make
sure that the indexed column is the one that you will be using to refin