[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,
[
https://issues.apache.org/jira/browse/DERBY-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483676
]
Suresh Thalamati commented on DERBY-378:
Thanks for your interest to document this issue Laura. Intially proposed spec
is attached to this jira (iexlobs.txt) , but it is out of date. I will update
the spec and post it in a day or two.
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.
[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,
[
https://issues.apache.org/jira/browse/DERBY-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483361
]
Laura Stewart commented on DERBY-378:
-
Suresh is there a spec for me to look at for this issue?
I'd like to understand the documentation hits.
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.
[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,
[
https://issues.apache.org/jira/browse/DERBY-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482479
]
Suresh Thalamati commented on DERBY-378:
Thanks for the feedback Army Mike. I agree with both of you ,
LOBS_FROM_EXTFILE/LOBS_TO_EXTFILE sounds better than
LOBS_IN_EXTFILE. Unless someone else has a better
suggestions. New procedure names will be :
SYSCS_UTIL.SYSCS_EXPORT_TABLE_LOBS_TO_EXTFILE(..)
SYSCS_UTIL.SYSCS_EXPORT_QUERY_LOBS_TO_EXTFILE(..)
2)This patch implements following two new procedure that allow
import of large object data stored in a external file.
(for example exported previously using the above export procedures).
SYSCS_UTIL.SYSCS_IMPORT_DATA_LOBS_FROM_EXTFILE(...)
SYSCS_UTIL.SYSCS_IMPORT_TABLE_LOBS_FROM_EXTFILE(..)
--
One another other thing I was debating myself was whether
to use EXTFILE or SEPFILE. Sticking with EXTFILE,
SEPFILE does not seem any better.
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.
[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,
[
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.
[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,
[
https://issues.apache.org/jira/browse/DERBY-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482500
]
Suresh Thalamati commented on DERBY-378:
Thanks for the feedback Laura. Incase of export EXTFILE is used
to indicate lob data is not stored in the main export file along with
other table data, but in a different file specified by the user. And incase of
import it indicates lobs data is in a different file, and the reference to
it is stored in the import file specified by the user.
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.
[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,
[
https://issues.apache.org/jira/browse/DERBY-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478840
]
Suresh Thalamati commented on DERBY-378:
Thanks for taking time to review , Dan.
1) I see use of StringUtil.fromHexString() in the patch, but no use of
StringUtil.toHexString() in the patch. How does the exporting work?
Export calls Resultset.getString() method for these types also. getString()
method
return the data in hex format, by calling StringUtil.toHexString().
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?
Good Catch. inserting nulls on malformed hex strings is bad. I will add a
a check for the return value from StringUtil.fromHexString() , and throw an
exception if it is null.
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.
[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,
[
https://issues.apache.org/jira/browse/DERBY-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478862
]
Suresh Thalamati commented on DERBY-378:
Committed derby378_2.diff to trunk on revision 515708..
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.
[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,
[
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.
[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,
[
https://issues.apache.org/jira/browse/DERBY-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475979
]
Suresh Thalamati commented on DERBY-378:
Each blob/clob goes into its own separate external file? Or all the
blobs/clobs go into a single external file?
[ Show ยป ] Bryan Pendleton [24/Feb/07 05:15 PM]
All the blobs/clobs go into a single external 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, 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.
[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,
[
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.
[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,
[
https://issues.apache.org/jira/browse/DERBY-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476056
]
Suresh Thalamati commented on DERBY-378:
Committed derby_378.diff to trunk on revision 512109. If there are any
review comments related to this patch , I will address them in the future
patches for this issue.
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.
[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,
[
https://issues.apache.org/jira/browse/DERBY-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475675
]
Bryan Pendleton commented on DERBY-378:
---
Each blob/clob goes into its own separate external file? Or all the blobs/clobs
go into a single external 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, 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.
[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,
[
http://issues.apache.org/jira/browse/DERBY-378?page=comments#action_12458976 ]
Daniel John Debrunner commented on DERBY-378:
-
For reading from a VTI I'm not sure why CLOB and BLOB are not supported.
SQLBlob seems to contain the correct code in its setValueFromResultSet(). It
might be a hangover from the time the codebase supported JDK 1.1 and
java.sql.Blobs were not available. It might be simply the work was never done.
What error do you get?
For setting BLOB/CLOB into a VTI it might be tricker, since it requires the SQL
layer to be able to manufacture a java.sql.Blob object, and since they are JDBC
objects the language doesn't handle them. Though it's a simiar problem to BLOBs
in triggers/functions and I think at least for triggers it works, so I think
there is a mechanism for creating a java.sql.Blob from a BLOB column.
and having written that, I thought BLOBs were used in triggers and triggers
used VTIs ...
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: http://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: 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[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,
[
http://issues.apache.org/jira/browse/DERBY-378?page=comments#action_12458978 ]
Suresh Thalamati commented on DERBY-378:
Thanks for the input Dan. When I specify the column type for import VTI as
Types.BLOB , I got the following error :
The external virtual table interface does not support BLOB or CLOB columns.
''{0}'' column ''{1}''.
This error is coming from impl/sql/compile/FromVti.java
if( columnType == Types.BLOB || columnType == Types.CLOB)
throw
StandardException.newException(SQLState.LANG_VTI_BLOB_CLOB_UNSUPPORTED,
getVTIName(), rsmd.getColumnName( i));
I will check out triggers with BLOBS.
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: http://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: 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[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,
[
http://issues.apache.org/jira/browse/DERBY-378?page=comments#action_12458981 ]
Daniel John Debrunner commented on DERBY-378:
-
DERBY-438 might lead you to the tests that show BLOBs in triggers work.
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: http://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: 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[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,
[
http://issues.apache.org/jira/browse/DERBY-378?page=comments#action_12458635 ]
Suresh Thalamati commented on DERBY-378:
related discussion on the derby-dev list:
http://www.nabble.com/%28DERBY-378%29-implementing--import-export-of-large-objects...-tf2515951.html#a7017509
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: http://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: 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[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,
[
http://issues.apache.org/jira/browse/DERBY-378?page=comments#action_12458636 ]
Suresh Thalamati commented on DERBY-378:
Import uses VTI to import data into a table from a file. Just found out
that derby does not support CLOB/BLOB data types with VTI. Any one remember
why these types are not supported ?
Currently all the columns in the import file are treated as VARCHAR type and
cast them to the appropriate column type of the table, when the insert
statement is generated. For example to import into a table T4(
create table t4( a int , b char(100)) );
INSERT INTO T4(A, B) --DERBY-PROPERTIES insertMode=bulkInsert
SELECT cast(COLUMN1 AS INTEGER) , COLUMN2 from new org.apache.derby.impl.load
d.Import('c:/suresht/databases/emp.dat',null,null,null, 2 ) AS importvti ;
Clob types column can casted from VARCHAR type, performance may be bad but it
will work.
Problem with blob data type is, it can be casted from any other type.
I am kind of stuck on how to extract the binary data from an import file and
insert
into the table using the VTI, without VTI support for CLOB/BLOB types.
types.
Any ideas/suggestions ?
Thanks
-suresh
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: http://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: 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[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,
[
http://issues.apache.org/jira/browse/DERBY-378?page=comments#action_12319071 ]
Brian Bonner commented on DERBY-378:
I agree with Suresh. There needs to be a way to import and export data from
clobs/blobs.
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: http://issues.apache.org/jira/browse/DERBY-378
Project: Derby
Type: Improvement
Components: Tools
Versions: 10.1.1.0
Reporter: Suresh Thalamati
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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
