Yeah, I finally figured that out a little while ago. I always thought
DESCRIBE was part of SQL. Go figure. Doesn't matter though. I had
DBI debugging turned on, and poring through the output helped me realize that
a prepare statement pulls in everything I'm looking for. All I had to do
was to dump the contents of $sth->{NAME} for each table. There's more I need
to do, but that's a good start.
Dave
"Michael A. Chase" wrote:
> It is exactly what the error message says. DESCRIBE is not a valid SQL
> statement, it is a SQL*Plus command.
> --
> Mac :})
> ** I normally forward private database questions to the DBI mail lists. **
> Give a hobbit a fish and he'll eat fish for a day.
> Give a hobbit a ring and he'll eat fish for an age.
> ----- Original Message -----
> From: "Dave Tamillow" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, April 06, 2001 6:04 AM
> Subject: [Fwd: Passing variables in DBD::Oracle]
>
> > P.S. While I'm at it, one other thing. How do you issue a DESCRIBE
> > statement through the DBI? I tried $dbh->do(q{ DESCRIBE ALL_TABLES});
> > and I get the following:
> >
> > DBD::Oracle::db do failed: ORA-00900: invalid SQL statement (DBD
> > ERROR: OCIStmtExecute) at db.pl line 18.
> >
> > I tried $dbh->prepare, but I get basically the same message.
