Re: Handling exceptions in saveChanges()
Re: Handling exceptions in saveChanges()
- Subject: Re: Handling exceptions in saveChanges()
- From: Art Isbell <email@hidden>
- Date: Mon, 16 Jun 2003 17:25:49 -1000
On Wednesday, June 11, 2003, at 06:32 AM, Jonathan Rochkind wrote:
Not a good general purpose solution, true, but in my own apps, I
decided that a 'last write wins' strategy is actually just fine. And
implementing it is easy as pie---simply turn off the lock icon for all
attributes but for primary key attributes,
Minor nit: I haven't found any reason to mark the primary key
attribute(s) as used for locking (has anyone?) because EOF must always
use it anyway to identify which row is being updated. Also, a primary
key attribute isn't normally a class property so it can't be updated
and shouldn't be even if it is a class property.
Aloha,
Art
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.