db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Thalamati (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-378) support for import/export of tables with clob/blob and the other binary data types will be good addition to derby,
Date Wed, 07 Mar 2007 01:29:24 GMT

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

Suresh Thalamati updated DERBY-378:
-----------------------------------

    Attachment: derby378_2.stat
                derby378_2.diff

DERBY -378 (partial)
This patch adds code required to support import/export of a table with
CHAR FOR BIT DATA, VARCHAR FOR BIT DATA,  LONG VARCHAR FOR BIT DATA
data types. Data of this type of columns is exported to the main export 
file as hex strings. On import data is also expected to be in hex strings 
in the main export file for these type of columns. This patch also 
disallows use of hex decimal characters (0-9 , a-f , A-F) as 
delimiters for import/export procedures. 

Maximum data length of these types is only  32700 ( 254 bytes for CHAR FOR 
BIT DATA , 32,672 for VARCHAR FOR BIT DATA and  32700 LONG VARCHAR FOR BIT DATA). Because
max length allowed is less than 32k, I think providing import/Export
using an external file for these types may not add much value. No external 
file support will be provided for these types. It can be added later, 
if some one thinks it is required. 

Tests:
Added a new junit test to test the import/export of these binary types. 

It would be great if someone can review this patch.  

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


Mime
View raw message