Hi Ramsey, I used to handle unique constraint violations via a custom editing context delegate in editingContextDidFailSaveChanges(). This worked fine, but since upgrading to a more recent Wonder, this no longer works (that method is never called on the delegate), and now I get a stack trace containing an ERXValidationException. I assume this is related to your commit here:
--- commit a3d8ae17480f04ff5b517c82fc3c864975c3af66 Author: nullterminated <[email protected]> Date: Thu Jun 7 21:33:44 2012 -0700 Add unique constraint handling to ERXSQLHelper for postgresql. --- (Until recently, the application in question was using Wonder dated prior to 7 June, so the timing fits, at least.) Could you explain how this new approach is supposed to work? I'm sure it's better than what I was doing, but at the moment it breaks my delegate approach, and it's not clear whether I need to change every application that depended on that, or whether there's another centralised approach I could use. -- Paul Hoadley http://logicsquad.net/ _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
