[
https://issues.apache.org/jira/browse/DERBY-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520358
]
Bryan Pendleton commented on DERBY-2888:
----------------------------------------
I modified BUG1.dbe to have enough data to cause a problem importing, and I
noticed that the IMPORT error message now *does* have the line number in it. I
get:
ERROR XIE0R: Import error on line 2 of file BUG1.dbe: Invalid character string
format for type INTEGER.
ERROR 22018: Invalid character string format for type INTEGER.
This appears to have been accomplished as part of DERBY-2193.
Aaron, can you try using Derby 10.3, which has the DERBY-2193 fix in it, and
let us know how it works for you?
> Useless error message during import: Invalid character string format for type
> INTEGER.
> --------------------------------------------------------------------------------------
>
> Key: DERBY-2888
> URL: https://issues.apache.org/jira/browse/DERBY-2888
> Project: Derby
> Issue Type: Improvement
> Components: Tools
> Affects Versions: 10.2.2.0
> Reporter: Aaron Digulla
> Priority: Minor
> Attachments: BUG1.dbe, BUG1.ddl
>
>
> When you try to import the attached data file into derby using
> SYSCS_UTIL.SYSCS_IMPORT_DATA('DERBY', 'BUG1', null, null, 'bug1.dbe', ';',
> '"', 'Cp1252', 1), you get the error: Invalid character string format for
> type INTEGER.' was thrown while evaluating an expression.
> If a table has many columns and many rows are imported, it is impossible to
> figure out where the error is in the input file. Please provide the column
> name and the line number in the error message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
