> The type in the PK column is NUMERIC with a size of 15 digits. This reflects
> what is in the Oracle database. But since NUMERIC isn't BIGINT, the key is
> being truncated to Integer. Is that expected behavior or have I found a bug?
Sure it is NUMERIC in DB, but you can still map it in Cayenn
The type in the PK column is NUMERIC with a size of 15 digits. This reflects
what is in the Oracle database. But since NUMERIC isn't BIGINT, the key is
being truncated to Integer. Is that expected behavior or have I found a bug?
This is no longer an urgent issue. I was already overriding OracleP
> How do I specify a primary key type to be BIGINT?
This is exactly what you need to do - in the Modeler change the PK column type
of DbEntity to BIGINT from INT.
Andrus
On Jul 20, 2012, at 3:19 AM, Joseph Senecal wrote:
> We're using Oracle and sequences, not an AUTO_PK table to generate
We're using Oracle and sequences, not an AUTO_PK table to generate the keys.
I've added logging into the custom code that pulls sequences, and the values
are right at that point. But when I look at the code that calls that, I find
right after the call:
if (pk.getType() == Types.BIGINT) {
Look at the columns widths of the AUTO_PK table?
Ari
On 20/07/12 10:07am, Joseph Senecal wrote:
We are using Cayenne 3.1 M3 in production. We have just discovered that the
primary keys being generated are being truncated to fit an int.
The sequence returns numbers like 5224748590. I've confir
We are using Cayenne 3.1 M3 in production. We have just discovered that the
primary keys being generated are being truncated to fit an int.
The sequence returns numbers like 5224748590. I've confirmed this by logging
the return value of LongPkRange.getNextPrimaryKey.
But the inserts are using P
