On Jul 30, 2007, at 10:19 , Tore Halset wrote:
I now found a similar problem, but I do not know if it is the same. Having a CHAR(2) as the meaningful primary key (yes, it is a bad idea...) makes cayenne (after upgrading to 3.0M1) throw away the value I set and create its own numeric value. As "200" and "201" does not fit in a CHAR(2) the database throws a SQLException.
Sorry. Forget this one. Created it myself... - Tore.
