Hi Amiel,
You can only get it if you are not using deferred constraints. If you
are using deferred constraints, the exception is only thrown at the
end of the transaction and EOF has no way of knowing which EO caused
the error. The best solution that I have found is to parse out the
table name and use that to infer the entity. If you are using single
table inheritance, this is not perfect, but as all entities in the
inheritance hierarchy will have to have the same constraint the error
is probably also consistent. If you can get the entity name, you can
then form a reasonable error message.
Chuck
On Jan 11, 2010, at 9:56 PM, Amiel Montecillo wrote:
Hi Everyone,
Is it possible to get the failed EO instance when an unique
constraint violation occurs? I have been digging in
EOGeneralAdaptorException but I couldn't figure out how to get the
instance of the EO that has failed.
Rgds,
Amiel
--
socket error: unable to connect to 127.0.0.1
_______________________________________________
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/chill%40global-village.net
This email sent to [email protected]
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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]
