[
https://issues.apache.org/jira/browse/DERBY-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520354
]
Bryan Pendleton commented on DERBY-2888:
----------------------------------------
What I've done in the past is to use a binary search technique:
- remove half the rows in your input file and see if the problem still occurs
- if it does, remove another half of the remaining rows
- if it doesn't, discard this half of the rows and switch to the other half of
the rows
You may have to conduct a few dozen experiments, but you'll find the bad row.
I agree, by the way, that including the actual row and column where the
exception occurred
would be extremely helpful. If I get some time this weekend, I'll have a look
at that code.
> 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.
