I have come across a problem with torque that may be brought up by my particular use:
Torque is unable to delete records that contain NULL values in fields that map to java primitive types - if you get the object then try Peer.delete(Object) - this is due to Torque filling in the criteria for delet from the object, which of course will set null primitives to a default value (ie int to "0"), which will not match with the null in the database. Many would argue (some here have) that these types of fields should not be null in the database - however, I am dealing with legacy databases and it cannot be avoided. Russell Smyth -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
