Re: What's is better solution for Lock? Use Timestamp or "mark all fields"
Re: What's is better solution for Lock? Use Timestamp or "mark all fields"
- Subject: Re: What's is better solution for Lock? Use Timestamp or "mark all fields"
- From: David Teran <email@hidden>
- Date: Tue, 1 Nov 2005 23:06:56 +0100
Depending on your database Timestamp fields don't always compare
equal. They often differ at the millisecond value.
For which databases is this true?
regards, David
IIRC, Postgresql and Oracle are the ones that have bitten people on
this mailing list. Or was it MySQL? Then again, maybe I am not
recalling correctly. That's what search engines are for
For PostgreSQL and for Oracle you can find Plugins in Project Wonder
which extend the plugins from WO, i've added some 'bugfixes' for
timestamps. The main issue is that the default plugin and the Oracle
plugin do not store milliseconds in the database.
Locking on a timestamp column is working without any problem, at
least if one uses these plugins from project wonder.
regards, David
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden