Re: DB uniqueness constraints and dealing with them
Re: DB uniqueness constraints and dealing with them
- Subject: Re: DB uniqueness constraints and dealing with them
- From: Mike Schrag <email@hidden>
- Date: Thu, 3 Jul 2008 14:35:14 -0400
While reading older discussions on dealing with DB uniqueness
restraints I've found out that the EOGeneralAdaptorException thrown
differs among databases. Is there some generic code that deals with
this in absolute terms ( don't you just *love* the word absolute
being used in conjunction with software :) ? If there is in WOnder,
could someone please be so kind to point me in the right direction
(which part of WOnder) so I can look at it?
Ah, looking over this I realize I do not say what I want the generic
code to do... All I want is find out for which key the uniqueness
constraint failed, so I can throw a validation exception.
Every database does this differently (and some are a huge pain to get
this info from -- like Oracle, for instance). I don't believe Wonder
has this code anywhere (that I've seen). I've been meaning to add
this to ERXSQLHelper, though.
ms
_______________________________________________
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