Thanks for the input.
 
I am implementing "TimeStampable" which returns a type "long". 
 
 
public class Student implements TimeStampable
{
    .........
 
    public void jdoSetTimeStamp(long l)
    {
        timeStamp = l;
    }
 
    public long jdoGetTimeStamp()
    {
        return timeStamp;
    }
}
 
 
As you have said derby support "bigint" not "long" data type.  But in my mapping file I did the mapping as follows:..........

<field name="timestamp" type="long">

<sql name="timestamp" type="bigint"/>

</field>

John.
 
 -----Original Message-----
From: Brian Schlining [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 14, 2006 12:07 PM
To: [email protected]
Subject: Re: [castor-user] BIGINT Support in Castor

I have a castor app that I've tested against both Derby and SQL Server. All the primary keys are bigints and the app works fine against both databases. The Castor mapping can be found at


Cheers
B

Hi Werner,

Quick question, does Castor support the sql type "BIGINT "?

My Derby database uses type "BIGINT" intead of "long"

Reported Run-time error:
org.exolab.castor.mapping.MappingException: Nested error:
org.exolab.castor.mapping.MappingException:
The SQL type BIGINT is not supported in this release



-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:

-------------------------------------------------


~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
Brian Schlining
MBARI
Software Engineer
(831)775-1855


Reply via email to