For example, we had this exact scenario due to the model specifying
varchar, and the type info not having a varchar, only a varchar2.
Since it didn't know what the column was, it didn't know how to
optimistically lock it, so it fell back to pessimistic locking. I
actually added some code to WO (I think its in 5.5 and an unreleased
5.4), which will log a warning when this occurs, since it was such a
PITA to track down when it happened to me (specifically it will warn
from JDBCAdaptor.isValidQualifierType).
i wonder if this shouldn't just throw an exception? is there ever a
case when you want to actually keep going when this happens?
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
