in reply to Re: Perl DBI-Related Error - really in the weeds
in thread Perl DBI-Related Error - really in the weeds

By the way, describe does work. I tried it before using it.
  • Comment on Re^2: Perl DBI-Related Error - really in the weeds

Replies are listed 'Best First'.
Re^3: Perl DBI-Related Error - really in the weeds
by runrig (Abbot) on Feb 23, 2006 at 01:01 UTC
    It worked in mysql or Oracle? (and how do you know it worked if you can't get it working?)

    Update: And some quick googling tells me that DESCRIBE is a SQL*Plus command, but not valid SQL. You can maybe use the DBI table_info method (or column_info? I don't know, I've never used either one) or select from one of the Oracle *_TABLES (*=DBA|ALL|USER) tables.

      It worked in oracle. I went into sqlplus from the server that has the oracle database and entered the sql command there.
Re^3: Perl DBI-Related Error - really in the weeds
by kwaping (Priest) on Feb 23, 2006 at 15:27 UTC
    For the record, I just tested a describe statement using working copies of DBI and Oracle. The statement fails on execute with this error:
    DBD::Oracle::st execute failed: ORA-00900: invalid SQL statement (DBD +ERROR: OCIStmtExecute) [for Statement "describe [schema.table removed + for security]"]