On Dec 18, 2005, at 10:01 AM, Stirling Olson wrote:
Notice the difference in digits on the timestamp values. This causes WO to think that the row has been updated outside the application so the update fails.
I've experienced similar problems with timestamp values on other databases as well. My only solution has been to eliminate float/ double/decimal and timestamp types as attributes used for locking in my eomodels.
Another workaround might be to limit the precision in which timestamp values are stored in a database. I.e., instead of storing the current timestamp which can be to milliseconds or even microseconds, use the current timestamp to create a new timestamp to the precision of seconds only, and store the new timestamp instead. Of course, this won't work for existing timestamp values or those stored by non-WO processes unless they also limit the precision to seconds.
Aloha, Art _______________________________________________ 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]
