[
https://issues.apache.org/jira/browse/DERBY-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478669
]
Daniel John Debrunner commented on DERBY-378:
---------------------------------------------
Looks good, couple of minor questions:
1) I see use of StringUtil.fromHexString() in the patch, but no use of
StringUtil.toHexString() in the patch. How does the exporting work?
2) If the input to StringUtil.fromHexString() is malformed by its length not
being a multiple of two then null will be silently inserted. Should import
throw an exception here?
These could be addressed after the patch is committed.
> support for import/export of tables with clob/blob and the other binary
> data types will be good addition to derby,
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-378
> URL: https://issues.apache.org/jira/browse/DERBY-378
> Project: Derby
> Issue Type: Improvement
> Components: Tools
> Affects Versions: 10.1.1.0
> Reporter: Suresh Thalamati
> Assigned To: Suresh Thalamati
> Attachments: derby378_1.diff, derby378_1.stat, derby378_2.diff,
> derby378_2.stat, iexlobs.txt
>
>
> Currently if I have a table that contains clob/blob column, import/export
> operations on that table
> throghs unsupported feature exception.
> set schema iep;
> set schema iep;
> create table ntype(a int , ct CLOB(1024));
> create table ntype1(bt BLOB(1024) , a int);
> call SYSCS_UTIL.SYSCS_EXPORT_TABLE ('iep', 'ntype' , 'extinout/ntype.dat' ,
> null, null, null) ;
> ERROR XIE0B: Column 'CT' in the table is of type CLOB, it is not supported by
> th
> e import/export feature.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
