RE: NULLS allowed FOREIGN keys short (SMALLINT) or byte(TINYINT)

2004-01-11 Thread Gerhard Otte
PROTECTED]; [EMAIL PROTECTED] Subject: NULLS allowed FOREIGN keys short (SMALLINT) or byte(TINYINT) hi! If a table has nulls allowed FOREIGN keys short (SMALLINT) or byte(TINYINT), Torque generating code and initializing these to a default value of 0. where 0(ZERO) is not valid value in foreign

NULLS allowed FOREIGN keys short (SMALLINT) or byte(TINYINT)

2004-01-09 Thread Annapareddy, Reddy (Contractor)
hi! If a table has nulls allowed FOREIGN keys short (SMALLINT) or byte(TINYINT), Torque generating code and initializing these to a default value of 0. where 0(ZERO) is not valid value in foreign keyed table. Causing update constrain conflict since torque using java primitive short/byte. In