No, not yet ... ;-). But it might as well turn into one ... ;-). But first, I need something to work with, a bug submission.
Werner wg> -----Original Message----- wg> From: John Greene [mailto:[EMAIL PROTECTED] wg> Sent: Tuesday, February 14, 2006 3:51 PM wg> To: Werner Guttmann wg> Subject: RE: [castor-user] BIGINT Support in Castor wg> wg> Werner, wg> wg> Looking at the mapping file I sent are you saying that this wg> is a valid bug issue? wg> wg> -----Original Message----- wg> From: Werner Guttmann [mailto:[EMAIL PROTECTED] wg> Sent: Tuesday, February 14, 2006 09:38 AM wg> To: [EMAIL PROTECTED] wg> Cc: [email protected] wg> Subject: RE: [castor-user] BIGINT Support in Castor wg> wg> wg> John, wg> wg> Can you please create a new Jira issue and attach a wg> complete Junit test case, if possible. Now, if that test wg> case followed the bug submission guidelines, it would be wg> even better .. ;-). wg> wg> Werner wg> wg> wg> -----Original Message----- wg> wg> From: John Greene [mailto:[EMAIL PROTECTED] wg> wg> Sent: Tuesday, February 14, 2006 3:26 PM wg> wg> To: Werner Guttmann wg> wg> Subject: RE: [castor-user] BIGINT Support in Castor wg> wg> wg> wg> Werner, wg> wg> wg> wg> I had already referred to the link wg> wg> http://castor.org/types.html#SQL-Type-Conversion. wg> wg> wg> wg> wg> wg> Please find mapping file below: wg> wg> wg> wg> wg> wg> <class name="Payments.Student" identity="id" wg> key-generator="MAX"> wg> wg> wg> wg> <map-to table="Student" /> wg> wg> <field name="id" type="int"> wg> wg> <sql name="id" type="integer"/> wg> wg> </field> wg> wg> wg> wg> <field name="name" type="string"> wg> wg> <sql name="name" type="varchar" /> wg> wg> </field> wg> wg> wg> wg> <field name="payment" type="Payments.Payment" wg> wg> collection="collection"> wg> wg> <sql many-key="id_student" /> wg> wg> </field> wg> wg> wg> wg> <field name="Group" type="Payments.Group" required="true"> wg> wg> <sql name="id_group"/> wg> wg> </field> wg> wg> wg> wg> <field name="timestamp" type="long"> wg> wg> <sql name="timestamp" type="bigint"/> wg> wg> </field> wg> wg> wg> wg> </class> wg> wg> wg> wg> -----Original Message----- wg> wg> From: Werner Guttmann [mailto:[EMAIL PROTECTED] wg> wg> Sent: Tuesday, February 14, 2006 09:03 AM wg> wg> To: [email protected]; [EMAIL PROTECTED] wg> wg> Subject: RE: [castor-user] BIGINT Support in Castor wg> wg> wg> wg> wg> wg> John, wg> wg> wg> wg> It should as explained at wg> wg> http://castor.org/types.html#SQL-Type-Conversion. wg> Having said that, wg> wg> can you please show us (by the means of a field wg> wg> mapping) what you are trying to achieve ? wg> wg> wg> wg> Werner wg> wg> wg> wg> wg> -----Original Message----- wg> wg> wg> From: John Greene [mailto:[EMAIL PROTECTED] wg> wg> wg> Sent: Tuesday, February 14, 2006 2:52 PM wg> wg> wg> To: Castor User wg> wg> wg> Subject: [castor-user] BIGINT Support in Castor wg> wg> wg> wg> wg> wg> Hi Werner, wg> wg> wg> wg> wg> wg> Quick question, does Castor support the sql type "BIGINT "? wg> wg> wg> wg> wg> wg> My Derby database uses type "BIGINT" intead of "long" wg> wg> wg> wg> wg> wg> Reported Run-time error: wg> wg> wg> org.exolab.castor.mapping.MappingException: wg> wg> Nested error: wg> wg> wg> org.exolab.castor.mapping.MappingException: wg> wg> wg> The SQL type BIGINT is not supported in this release wg> wg> wg> wg> wg> wg> wg> wg> wg> wg> wg> wg> ------------------------------------------------- wg> wg> wg> If you wish to unsubscribe from this list, please wg> send an empty wg> wg> wg> message to the following address: wg> wg> wg> wg> wg> wg> [EMAIL PROTECTED] wg> wg> wg> ------------------------------------------------- wg> wg> wg> wg> wg> wg> wg> wg> wg> wg> wg> wg> wg> wg> wg> ------------------------------------------------- If you wish to unsubscribe from this list, please send an empty message to the following address: [EMAIL PROTECTED] -------------------------------------------------
