I was looking through mountains of log entries the other day, and noticed that when I execute a call like:
ObjPeer.doDelete(obj); Torque generates a where clause that includes every column/value pair, instead of just using the primary key. This has the side effect of not deleting the object if it has changed in the database since it was loaded by Torque. It also makes the database work harder, since it has to match every field, not just the PK. Is there any reason for Torque to work this way? Would people object to a patch to fix it (if possible)? -james -- [] James A. Hillyerd <[EMAIL PROTECTED]> - Java Software Engineer [] PGP 1024D/D31BC40D F87B 7906 C0DA 32E8 B8F6 DE23 FBF6 4712 D31B C40D -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
