db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A B (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-378) support for import/export of tables with clob/blob and the other binary data types will be good addition to derby,
Date Mon, 26 Feb 2007 21:36:05 GMT

    [ https://issues.apache.org/jira/browse/DERBY-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476009
] 

A B commented on DERBY-378:
---------------------------

I haven't actually reviewed the code at all, but I was just wondering about the names for
the new procedures.  When I first looked at them use of the "IN_EXTFILE" sounded a tad awkward
to me (esp. for export).  I instinctively thought "...TO_EXTFILE" would be better for export
and "FROM_EXTFILE" would be better for import.  But then I realized that such names could
potentially cause confusion (ex. If I'm importing lobs from EXTFILE does that mean there is
other, non-lob data in EXTFILE that I'm not importing?)  So those probably aren't much better.

The only other thing that comes to mind is "USING_EXTFILE", but again, I don't know if that's
really any better.  Perhaps "IN_EXTFILE" is in fact best because it's generic and it's short,
in which case please feel free to leave the procedure names as they are.  I just thought I'd
mention that on first reading the names seemed slightly odd, in case you or anyone else can
come up with other suggestions.

NOTE: I do *not* think this little comment should block commit of the patch.  This is a pretty
minor thing and could easily be changed as part of a follow-up patch when (and if) a different
set of names is chosen.

> 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, 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.


Mime
View raw message