I also totally missed IntegerType in the stack trace. 😕
On Wed, Nov 13, 2019 at 8:42 AM Michael Gentry wrote:
> Hi Andrus,
>
> I was basing my response due to the "Numeric Overflow" exception, which
> sounds like a number too big to fit into a Long. If a BIGINT/BigInteger
> will work, that's
Hi Andrus,
I was basing my response due to the "Numeric Overflow" exception, which
sounds like a number too big to fit into a Long. If a BIGINT/BigInteger
will work, that's the easiest solution.
On Wed, Nov 13, 2019 at 8:35 AM Andrus Adamchik
wrote:
> This still does not invalidate the origin
This still does not invalidate the original question though - why wouldn't
Cayenne choose a Long here?
My suggestion is to map this column as BIGINT in Cayenne, and it will do the
right thing.
Andrus
> On Nov 13, 2019, at 4:29 PM, Michael Gentry wrote:
>
> Hi Vemund!
>
> Long.MAX_VALUE is
Hi Vemund!
Long.MAX_VALUE is 9,223,372,036,854,775,807. NUMBER(38) is a lot more
digits.
Does your DB really have primary keys that large? To play Devil's Advocate:
9223372036854775807 / 1000 inserts/second / 60 seconds/minute / 60
minutes/hour / 24 hours/day / 365 days/year = 292,471,208 year
Hi,
I'm running a Oracle database and trying to get Cayenne to work when having
primary keys that should be mapped to Long in Java. The data type in Oracle is
NUMBER(38), but when I create a SelectQuery and use DlpObject object=
(DlpObject) Cayenne.objectForQuery(ctx, this); to get the object,
