Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "OJB Developers List" <ojb-dev@db.apache.org>
Message-ID: <4017DD45.7090001@olin.edu>
Date: Wed, 28 Jan 2004 11:03:17 -0500
From: Gus Heck <gus.heck@olin.edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20030917
MIME-Version: 1.0
To: OJB Developers List <ojb-dev@db.apache.org>
Subject: Re: torqueschema bug?
References: <Pine.GSO.4.21.0401272255280.12152-100000@pille>
In-Reply-To: <Pine.GSO.4.21.0401272255280.12152-100000@pille>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hmm, I am using MySQL 4.0.14-standard with databaseDriver = 
org.gjt.mm.mysql.Driver downloaded from thier site at the same time. The 
exception I got contained the message containing the usual your sql 
stinks message  (there is a problem with your syntax near "LONGVARBINARY 
Address" etc) (that is by memory not a paste).

If I have some time later I will see if I can't do the test you describe.

- Gus

Thomas Dudziak wrote:

>On Tue, 27 Jan 2004, Gus Heck wrote:
>
>  
>
>>Not sure if this is the right place to post this, but here goes...
>>
>>I had an interesting experience with torque recently... I had a field 
>>that was a nonpersistant class, and torqueshcema decided that it should 
>>be stored as type "LONGVARBINARY". This caused problems, as when my code 
>>tried to push that into MySQL 4 it choked probably because (according to 
>>my MySQL book) MySQL expects it to be "LONG VARBINARY" (note the space) 
>>or "MEDIUMBLOB".
>>    
>>
>
>In the torque schema, LONGVARBINARY is correct (see dtd at
>http://db.apache.org/torque/generator/database.dtd.txt). The XDoclet OJB
>module uses it when it encounters an not-persistent datatype without a
>predefined mapping.
>As for mysql, I'm not sure whether LONG VARBINARY would be correct
>either. The manual defines neither but mentions that myODBC defines
>LONGVARBINARY for BLOBs (http://www.mysql.com/doc/en/BLOB.html) which
>might also affect the jdbc driver.
>
>So this might be a bug in torque, or a problem with your MySQL version
>(or jdbc-driver which probably does the mapping) ?
>If you're unsure, you could create a simple table with a LONGVARBINARY
>column using with the 'sql' ant task and your jdbc driver and settings.
>
>Tom
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>  
>


---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org