[
https://issues.apache.org/jira/browse/DERBY-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482488
]
Laura Stewart commented on DERBY-378:
-------------------------------------
These procedure names are fine with me. The names are clear (Export To and
Import From),
and they stay under 50 characters including underscores and the period (just
barely :-)
More than 50 can cause real problems in the PDF output. The name can get
truncated.
I'm assuming the EXTFILE refers to External File, as opposed to a separate file?
I think EXTFILE is better too.
> 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, derby378_4.diff,
> derby378_4.stat, derby378_5.diff, 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.
