[
https://issues.apache.org/jira/browse/DERBY-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-2858:
--------------------------------------
Attachment: link.diff
Perhaps linking the exceptions is enough? The attached, untested patch prints
this for the same call:
ij> call SYSCS_UTIL.SYSCS_EXPORT_TABLE
(
'APP',
'LOBTABLE',
'/unknown/test-export-table.dat',
null,
null,
null
);
ERROR XIE0I: An IOException occurred while writing data to the file.
ERROR XJ001: Java exception: '/unknown/test-export-table.dat (No such file or
directory): java.io.FileNotFoundException'.
> Export exceptions swallow useful information
> --------------------------------------------
>
> Key: DERBY-2858
> URL: https://issues.apache.org/jira/browse/DERBY-2858
> Project: Derby
> Issue Type: Bug
> Components: Tools
> Affects Versions: 10.3.1.0
> Reporter: Rick Hillegas
> Priority: Minor
> Attachments: link.diff
>
>
> If you try to export a table to a nonexistent directory, you get a
> SQLException which tells you that an IOException occurred. The actual
> IOException tells you that the file or directory can't be found. That is
> useful information and ought to appear in the message text of the
> SQLException. E.g.:
> j> call SYSCS_UTIL.SYSCS_EXPORT_TABLE
> (
> 'APP',
> 'LOBTABLE',
> '/unknown/test-export-table.dat',
> null,
> null,
> null
> );
> ERROR XIE0I: An IOException occurred while writing data to the file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
