I probably did have issues but I did get my original uniqueness check
working 'good enough' but my biggest motivation was performance.
Originally I was checking for uniqueness in my validateKeys() by doing
fetches to get the latest from the DB ( I can see folks wincing right
now at the thought ). This was way before I understood just how often
those validation methods get called and therefore how expensive that
is to be doing.
Leaving it to the db at the very latest seems to be a very efficient
and fairly elegant way of looking after this and things certainly now
feel 'snappier'
Am 27.05.2008 um 20:05 schrieb Chuck Hill: The thing is, as I expect
Paul has found out, is that this won't work reliably. Something else
can add the value to the database between when you make this check
and when the SQL transaction is committed. ... [...]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
