[
https://issues.apache.org/jira/browse/DERBY-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Thalamati updated DERBY-378:
-----------------------------------
Attachment: derby378_3.stat
derby378_3.diff
DERBY -378 (partial)
This patch checks for invalid hex strings in the import file
while performing import into a table with CHAR FOR BIT DATA,
VARCHAR FOR BIT DATA, LONG VARCHAR FOR BIT DATA data types.
Import will throw an exception if it detects any invalid hex
strings during import.
Tests:
Added a new junit test case to ImportExportBinaryDataTest.java
to test for the invalid hex strings in the import file.
> 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, derby378_3.diff, derby378_3.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.
