Neil, think about locking on attributes that should not change, or
ones that you want your update to fail if they have changed since your
data was last fetched. Depending on each entity, you will probably
have different criteria --- from turning on all locks to turning off
all but the id.
I know some versions of DBs can create problems with timestamps. Your
DB may require that you turn off all locks on timestamps, which is
unfortunate if you do need a lock on that attribute.
Check your model with regards to BigDecimal. If your scale is set
correctly, I don't believe you should have any trouble with those.
-George
On Nov 23, 2008, at 5:51 AM, Neil MacLennan wrote:
Quote:
I tend to just turn off locking for those columns where there are
time-stamps and non-integral numerical values.
In response to my BigDecimal WOes thread I got another comment,
above, on turning off column locks on time-stamps and non-integral
values. You didn't see this comment, if came (accidentally I assume)
off-list.
Can I ask what other column types folks tend to turn off locking
for? Is there an optimum combination? Int-types only?
The 'starter for 10' [UK-only idiom?] is:
- Timestamps
- Float/Decimal
- BLOB
Any others? Any disagreement on the above?
.neilmac
_______________________________________________
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/george%40boxofficetickets.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
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]
