• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: How to get the failing EO when a unique constraint violation occurs?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to get the failing EO when a unique constraint violation occurs?


  • Subject: Re: How to get the failing EO when a unique constraint violation occurs?
  • From: Chuck Hill <email@hidden>
  • Date: Wed, 13 Jan 2010 17:12:47 -0800


On Jan 12, 2010, at 4:37 PM, Amiel Montecillo wrote:

@Ramsey, yeah I had the feeling I might end up with gray hairs trying to find that EO too so I am going with the index name.

@Chuck - I didn't have to get the table name to get an entity. I notice I can get the EOAdaptorOperation that exposes the entity.

That sounds like you are NOT using deferred constraints. In that case, you should be able to get the EO. Have a look at our validation framework (http://www.global-village.net/chill/gvc_frameworks) for how.



Here is what I have so far.

@Override
public boolean handleDatabaseException(EODatabaseContext databaseContext, Throwable throwable) {
if(throwable instanceof EOGeneralAdaptorException) {
EOGeneralAdaptorException e = (EOGeneralAdaptorException)throwable;


EOAdaptorOperation failedOp = (EOAdaptorOperation )e .userInfo().objectForKey(EOAdaptorChannel.FailedAdaptorOperationKey);
if(failedOp != null && failedOp.exception() instanceof JDBCAdaptorException) {
JDBCAdaptorException ae = (JDBCAdaptorException)failedOp.exception();


                //see oracle error codes
                switch(ae.sqlException().getErrorCode()) {

case 1: //Violates unique constraint ORA-00001
Matcher m = Pattern.compile("\\(.*(\\..+)\ \)").matcher(ae.sqlException().getMessage());
if (m.find()) {
throw ERXValidationFactory.defaultFactory().createException(null,
null, null, failedOp.entity().name() + m.group(1));
}


}
}
}
return super.handleDatabaseException(databaseContext, throwable);
}



Question is, will there always be an EOAdaptorOperation that exposes the entity taken from userInfo? "Coz this code is useless if it's not guaranteed and will have to use your ERXEOAccessUtilities.entityUsingTable().

I'd expect that to only be available if the constraint was not deferred. For some constraints, you need to defer the checking of the constraint until commit as EOF does not send operations to the database in the same order they happened in Java. So if the row matching the constraint is changing, but still unique, you can get incorrect failures when not deferring the check.



Chuck

On Wed, Jan 13, 2010 at 8:19 AM, Ramsey Lee Gurley <email@hidden> wrote:
Hi Amiel,


That's basically what I'm doing with Postgresql right now too. I managed to retrieve an EO if the operation is updating the EO instead of creating one. I cheated and used the editingContext for the database context from _databaseContextState().objectForKey("editingContext"). Even then, I was unable to use that context to retrieve the object if it is a new EO. Given Chuck's mention of deferred constraints, I could see how that might throw another wrench into the process. I was expecting to use the bindings from the statement that failed to figure out which EO to grab.

Anyway, at this point, I've pretty much given up hope on retrieving the EO. I spent waaaay too long trying to find a cure for that problem. (^^) An index name is at least sufficient to return a somewhat informative message.

Ramsey

On Jan 12, 2010, at 1:26 AM, Amiel Montecillo wrote:

> Hi Chuck,
>
> I'm not sure if I got you correctly (english is not my natural language). But this what I am doing:
>
> 1. Determine the unique constraint violation exception
>
> 2. Get the table and constraint name
>
> Next exception:SQL State:23000 -- error code: 1 -- msg: ORA-00001: unique constraint (WATCHLISTDEV.WATCHLISTUSER_CON_UEMAIL) violated
>
> 3. throw new ERXValidationException(constraintName, null, null);
>
> 4. In ValidationTemplate.strings:
>
> WATCHLISTDEV.WATCHLISTUSER_CON_UEMAIL = "This email address is already taken.";
>
> It works, but I am not sure this is the best way.
>
> Amiel
>
> On Tue, Jan 12, 2010 at 2:07 PM, Chuck Hill <email@hidden > wrote:
> 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@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>
> --
> 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
>
>
>
>
>
>
>
>
>
>
> --
> 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@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden





-- 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@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden

-- 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@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >How to get the failing EO when a unique constraint violation occurs? (From: Amiel Montecillo <email@hidden>)
 >Re: How to get the failing EO when a unique constraint violation occurs? (From: Chuck Hill <email@hidden>)
 >Re: How to get the failing EO when a unique constraint violation occurs? (From: Amiel Montecillo <email@hidden>)
 >Re: How to get the failing EO when a unique constraint violation occurs? (From: Ramsey Lee Gurley <email@hidden>)
 >Re: How to get the failing EO when a unique constraint violation occurs? (From: Amiel Montecillo <email@hidden>)

  • Prev by Date: Re: Modeling an optional to-one relationship
  • Next by Date: Re: Modeling an optional to-one relationship
  • Previous by thread: Re: How to get the failing EO when a unique constraint violation occurs?
  • Next by thread: [MEET] January WO-NoVA meeting NEXT TUESDAY (1/19/2010)
  • Index(es):
    • Date
    • Thread