db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Watzek <mwa.t...@spree.de>
Subject Re: JIRA JDO-68
Date Wed, 03 Aug 2005 10:30:34 GMT
Hi Andy,

I found the problem:

I had prepared the ORM metadata for class "FieldsOfCharacter" in another 
local workspace. Mistakenly, I made a stupid copy/paste mistake copying 
wrong metadata for class "FieldsOfCharacter" into my current workspace: 
I copied the contents of file "FieldsOfPrimitivechar-derby.orm" to file 

Fixing this, test "TestFieldsOfCharacter" successfully passes.

One question: JPOX does not complain if the ORM metadata for a class 
specifies fields which do not exist in that class. Would it be an option 
to throw a JDOFatalUserException("ORM metadata of class XXX specifies 
column mapping for field YYY. This field does not exist in the class.") 
in this case?


>>I changed the column types of table "FIELDSOFCHARACTER" back to INTEGER.
>>I also changed the ORM metadata for class "FieldsOfCharacter", e.g.
>>I'm using JPOX nightly build 2005-08-01. Can you please check and verify
>>if JPOX calls "PrepraredStatement.setString" for the case above?
> Hi Michael,
> It's not in SVN. When it's in SVN then I'll have a look.
> For the record on the issue of CHAR(1) or INTEGER, I'm not too fussed whether 
> we have CHAR(1), or INTEGER or whatever - all I want is consistent metadata 
> and schema so it's a fair test.

Michael Watzek                  Tech@Spree Engineering GmbH
mailto:mwa.tech@spree.de        Buelowstr. 66
Tel.:  ++49/30/235 520 36       10783 Berlin - Germany
Fax.:  ++49/30/217 520 12       http://www.spree.de/

View raw message