Re: EOF operation ordering
Re: EOF operation ordering
- Subject: Re: EOF operation ordering
- From: Chuck Hill <email@hidden>
- Date: Tue, 19 Feb 2008 08:07:16 -0800
I don't ever recall WO/EOF ordering the operations correctly in any
dependable manner. Either you do it in your code, or it is subject
to the whims of EOF implementation.
I wrote these classes so that I could use MS SQLServer which does not
support deferred constraints. See these Wonder classes:
com.webobjects.eoaccess.ERXEntityDependencyOrderingDelegate
com.webobjects.eoaccess.ERXAdaptorOpComparator
er.extensions.eoaccess.entityordering.ERXEntityOrder
er.extensions.eoaccess.entityordering.ERXEntityFKConstraintOrder
er.extensions.eoaccess.ERXDatabaseContextMulticastingDelegate
I use this with Single Table inheritance and it works. It work (I
think) with Vertical Inheritance (thanks to David Avendasora). I
think there are still some glitches with Horizontal Inheritance. Bug
reports welcome! Bug reports with example model and code very welcome!
Chuck
On Feb 19, 2008, at 7:56 AM, Mike Schrag wrote:
Chuck wrote an operation ordering delegate in Wonder to support
MSSQL (which doesn't support deferrable) that might be helpful here.
ms
On Feb 19, 2008, at 10:43 AM, Dov Rosenberg wrote:
We have had to resort to deferred constraints for Oracle. For SQL
Server we
have had to disable the constraints. I am certainly interested in
a more
portable solution.
Dov Rosenberg
On 2/19/08 10:37 AM, "Pierre Bernard" <webobjects-
email@hidden> wrote:
Hi!
Back in the day of WO 4.5 to WO 5.1, I worked on a project where we
relied on EOF's capability to order database operations. Actually we
even extended the mechanism using a database context delegate to
apply
further sorting to already sorted operations.
On more recent projects, I always set contraints to be deferrable
and
was thus not bothered by problems of operation ordering.
Today, I get a call from a former colleague who wants a new
project to
be set up like past common project: non deferrable constraints.
It turns out that on WO 5.2 this doesn't seem to work as
expected. The
database complains as the operations are not correctly ordered.
Did WO 5.2 break operation ordering? Has it become optional?
(I have not seen the EOModel in question. I wonder if it has
circular
references which may prevent proper ordering.)
Show of hands: who uses deferrable constraints, who relies on
operation ordering?
Pierre
- - -
Houdah Software s. à r. l.
http://www.houdah.com
HoudahGeo: One-stop photo geocoding
HoudahSpot: Powerful Spotlight frontend
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40inquira.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mdimension.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40global-village.net
This email sent to email@hidden
--
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