Handeling DB Unique Constraints
Handeling DB Unique Constraints
- Subject: Handeling DB Unique Constraints
- From: David Avendasora <email@hidden>
- Date: Tue, 24 Nov 2009 15:17:23 -0500
| Hi all,
I've found a few places where people discuss what the best way to handle GeneralAdapterExceptions triggered by violation of a unique constraint on a given table.
The last I found about it (from May, 2008) was a discussion about using an ERXEC delegate, which in turn would use the DB specific ERXSQLHelper.
Did anyone ever actually implement this? We have several places in our code where we are handling the exception in the component, which is a horrible place to put it from a MVC perspective as it makes our components dependent upon our DB's error message (I can hear you screaming from here, Chuck).
I'd really like to do this right, but I think the exact execution is a bit over my head, so I'm hoping someone else has actually gone ahead and did some of it already!
Thanks,
Dave
|
_______________________________________________
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