On Fri, 9 Jun 2006 01:17:06 -0400, Jeffrey Seger wrote:
Hi Jeffrey
So a similar query to what you are looking for in table_info is:
select table_name, owner from all_tables where table_name like
'%STATE%';
Hmmm.
SQL select table_name, owner from all_tables where table_name like '%STATE%';
On Fri, 12 May 2006 14:39:02 +1000, Ron Savage wrote:
Hi Ron
Just for the archives:
When I connect via Perl, eg using:
dsn=dbi:ODBC:dsn_name
I get this error:
DBI connect('dsn_name','system',...) failed: Specified driver could
not be loaded due to system error 1114 (Oracle in XE). (SQL-
Hi,
I'm using DBD::DB2 0.78 and DBI 1.51. I am finding that code which is working
to DBD::ODBC and DBD::mysql fails with invalid cursor state but inserting a
call to finish makes it work. Up until now, I've never used finish because the
docs say:
If execute() is called on a statement handle
I
On Jun 9, 2006, at 2:08 AM, Ron Savage wrote:
On Fri, 9 Jun 2006 01:17:06 -0400, Jeffrey Seger wrote:
So a similar query to what you are looking for in table_info is:
select table_name, owner from all_tables where table_name like
'%STATE%';
Hmmm.
SQL select table_name, owner from
WAG here: will the DBD::DB2 driver implicitly finish the resources if
you try calling $sth-fetchrow_array() again?
I don't know if DBD::DB2 can know whether there are more rows left in
the result set until you try fetching the next row, ergo it keeps the
statement handle active.
Dan
On
On 09-Jun-2006 Dan Scott wrote:
WAG here: will the DBD::DB2 driver implicitly finish the resources if
you try calling $sth-fetchrow_array() again?
Yes.
I don't know if DBD::DB2 can know whether there are more rows left in
the result set until you try fetching the next row, ergo it keeps the
Just for the sake of completeness, are you logging in as 'SYSTEM' in
your perl script?
Or are you logging in as a user which might not have permission to
see the table?
-Chris
In his original post, he did show that he was logged in, at least on
sqlplus, as system. I assumed he was in
On Fri, 9 Jun 2006 15:13:04 -0400, Jeffrey Seger wrote:
Hi Jeffrey et al
Just for the sake of completeness, are you logging in as 'SYSTEM'
in your perl script?
Or are you logging in as a user which might not have permission
to see the table?
I'm logging in as 'system' to create all tables,