Wow. I'm shocked and horrified that they made the database table name
not simply case-sensitive (remember, my table test was created
lowercase), but uppercase only. It wasn't the case of the procedure, but
the table name. This:
ij> call syscs_util.syscs_import_table(null, 'TEST', 'zipcodes.csv',
null, null, null, 1);
worked. Thanks Scotto for the tip!
________________________________
From: scotto [mailto:scotto@mitsonline.com]
Sent: Friday, August 12, 2005 3:19 PM
To: Delaune, Todd I
Subject: RE: Derby 10.1.1.0 SYSCS_UTIL.SYSCS_IMPORT_TABLE bug
Watch your case sensitivity. I had the same problems. Make everything
uppercase in the stored proc call and it should work.
--scott
________________________________
From: Delaune, Todd I [mailto:tidelaune@Trinsic.com]
Sent: Wednesday, August 10, 2005 7:53 AM
To: derby-user@db.apache.org
Subject: Derby 10.1.1.0 SYSCS_UTIL.SYSCS_IMPORT_TABLE bug
I noticed a problem with the built-in system procedure,
SYSCS_UTIL.SYSCS_IMPORT_TABLE. Under 10.0.2.1 this procedure works fine,
however the new version consistently produces table not found errors. As
you can see below, the table test does exist, however the procedure
doesn't acknolwedge it:
ij> create table test (col integer);
0 rows inserted/updated/deleted
ij> select * from test;
COL
-----------
0 rows selected
ij> call syscs_util.syscs_import_table(null, 'test', 'somefile', null,
null, null, 1);
ERROR XIE0M: Table 'test' does not exist.
I've been unable to find any other reference to this problem. I've
tested it with the old and new versions, using brand new databases, and
consistently the procedure fails only in 10.1.1.0. Perhaps it's related
to the 208770 patch?
(http://www.mail-archive.com/derby-dev@db.apache.org/msg06411.html)
Thanks in advance,
Todd Delaune
|