[
https://issues.apache.org/jira/browse/DERBY-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178860#comment-13178860
]
Knut Anders Hatlen commented on DERBY-5337:
-------------------------------------------
I tried to reproduce this problem with Derby 10.8.2.2 by creating a file called
704.dat with these two lines:
1,2
3,4
And then I successfully invoked the import procedure:
ij> CREATE TABLE "DBA"."TEST" (
"ID" integer NOT NULL
,"Descendant" integer NOT NULL
,PRIMARY KEY ("ID","Descendant")
);
0 rows inserted/updated/deleted
ij> CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE('DBA', 'TEST', '704.dat', ',', '"',
'UTF-8',0);
0 rows inserted/updated/deleted
ij> SELECT * FROM DBA.TEST;
ID |Descendant
-----------------------
1 |2
3 |4
2 rows selected
I only see the same exception as the one mentioned in the bug description if
the 704.dat file contains fewer columns than the actual table. You don't happen
to still have the data file lying around so that you can verify that every line
in the file contains exactly two integers separated by a comma, do you?
> Encountering error when importing to table using CALL
> SYSCS_UTIL.SYSCS_IMPORT_TABLE
> -----------------------------------------------------------------------------------
>
> Key: DERBY-5337
> URL: https://issues.apache.org/jira/browse/DERBY-5337
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.8.1.2
> Environment: 3GB RAM, Windows XP SP3, Core i-5
> Reporter: Ranjit Aneesh
>
> I am encountering the following issue when trying to call CALL
> SYSCS_UTIL.SYSCS_IMPORT_TABLE.
> I am passing the schema name as has been pointed out as a possible cause
> conflicting with multiple tables with the same name.
> The actual error is :
> CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE('DBA', 'TEST', 'C:/temp/unload/704.dat',
> ',', '"', 'UTF-8',0)
> The exception 'java.sql.SQLException: Column 'COLUMN2' is either not in any
> table in the FROM list or appears within a join specification and is outside
> the scope of the join specification or appears in a HAVING clause and is not
> in the GROUP BY list. If this is a CREATE or ALTER TABLE statement then
> 'COLUMN2' is not a column in the target table.' was thrown while evaluating
> an expression.
> This issue I am encountering in the 10.8.1.2 version of derby. I am using
> embedded driver
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
