Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cayenne.apache.org
Date: Tue, 25 Oct 2016 06:05:07 -0700 (MST)
From: fael <peter.hvass@jamesinnes.com>
To: user@cayenne.apache.org
Message-ID: <1477400707522-4028228.post@n3.nabble.com>
Subject: [4.0M3-SNAPSHOT] Modeller and UNSIGNED BIGINT
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Tue, 25 Oct 2016 13:05:23 -0000

Hello all,

I was using Cayenne's baked in AUTO_PK_SUPPORT up till very recently.

Have now switched to use database-generated keys - I'm using the MySQL
driver.

My keys are all defined in MySQL as BIGINT(20) UNSIGNED NOT NULL
AUTO_INCREMENT.

Foreign key fields are defined as BIGINT(20) UNSIGNED (sometimes NOT NULL).

I was really pleased to see that for new DbEntity items when I correctly set
the PK Generation Strategy an 'AUTO_INCREMENT' is added to the generated SQL
when migrating!!

I did hit a wall when trying to set a DbEntity attribute type to be
specifically an UNSIGNED BIGINT; can't seem to do this and therefore can't
use the modeller to migrate for my UNSIGNED BIGINT.

Even if this may not be something worth adding in - I wondered whether there
was any way I might override or configure to achieve this.

Many thanks,
Peter


--
View this message in context: http://cayenne.195.n3.nabble.com/4-0M3-SNAPSHOT-Modeller-and-UNSIGNED-BIGINT-tp4028228.html
Sent from the Cayenne - User mailing list archive at Nabble.com.