Mailing-List: contact ddlutils-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ddlutils-dev@db.apache.org
Message-ID: <33485686.1150300350183.JavaMail.jira@brutus>
Date: Wed, 14 Jun 2006 15:52:30 +0000 (GMT+00:00)
From: "Guy Davis (JIRA)" <jira@apache.org>
To: ddlutils-dev@db.apache.org
Subject: [jira] Commented: (DDLUTILS-100) WriteDataToFile command not
 handling BLOBs correctly
In-Reply-To: <1888452.1145497055063.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DDLUTILS-100?page=comments#action_12416221 ] 

Guy Davis commented on DDLUTILS-100:
------------------------------------

I just did a full update of the latest DDLUtils source from SVN.  I had to resolve a conflict in org.apache.commons.codec.binary.Base64.ByteArrayBase64Converter with my patch as recent changes had been made here.  I resolved the conflict, but couldn't help but notice that you're encoding in the convertFromString() and decoding in convertToString().  

This seems backwards.  I have this corrected in my previous patch which works great for us with our BLOB columns in Oracle 10g databases.

> WriteDataToFile command not handling BLOBs correctly
> ----------------------------------------------------
>
>          Key: DDLUTILS-100
>          URL: http://issues.apache.org/jira/browse/DDLUTILS-100
>      Project: DdlUtils
>         Type: Bug

>   Components: Ant Tasks
>  Environment: Win XP SP2
> Java 1.5.0_06
> Oracle 10g EE
>     Reporter: Guy Davis
>     Assignee: Thomas Dudziak
>     Priority: Minor
>  Attachments: blob.patch
>
> We recently added a table with a BLOB column to our application.  We use DDLUtils for dumping the schema and data to XML,  versioning the XML files, and also loading back into clean databases.  Unfortunately, the dump for the BLOB table just called toString() on the BLOB object itself which meant the BLOB data was lost.

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