Suresh Thalamati wrote:
BLOB:
o Blob data is written to export file as it is stored in the database,
it is not converted to hex or any another format. character code-set
conversion is not done for the binary data.
o If the data contains the delimiters , then it will be a problem if
stored in the same file with other data types. It may not be such a good
idea to attempt to interpret binary data to find the delimiters inside
the data and inject double delimiters into the data. That leaves us with
following two options :
1) Allow import/export of blob data only when they it is stored in an
external file.
2) Write the blob data to the export file along with other data types
during export, assuming the blob data does not contain any delimiters
and throw an error if on import if it finds delimiters inside the data,
by interpreting it using the same code-set as the other character data.
I say option 1) and I assume it's for all binary data, not just BLOB,
e.g. VARCHAR FOR BIT DATA etc. Seems like with binary data the chance of
having a problematic character in the text file is close to 100%.
Dan.
- Re: (DERBY-378) implementing import/export of large... Daniel John Debrunner
-
