But SQL has an additional state:: null. And there's a difference between calling a torque set method, and not calling a set method. So the question remains: is Torque's behavior documented? Does Torque support null column values for primitive type columns (e.g. columns other than String and NumberKey)?
> What you find here is the Java default behavior. A int has a default > value of 0. It can not be set to null. Therefore when the value is > initialized and no other value is given it is set to 0. Same applies to > long. > -- View this message in context: http://www.nabble.com/Question%3A-Torque-NULL-handling-on-insert%2C-update-tf4709373.html#a13462606 Sent from the Apache DB - Torque Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
