You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by Michael Gentry <mg...@masslight.net> on 2011/08/01 15:13:21 UTC
Re: Ashwood Issues
BTW Andrus, the algorithm I was using in my entity sorter had a pretty
significant flaw, so I'm going to have to restart it at some point.
However, it did help us find a deep DbEntity cycle that was messing
Ashwood up. We had something like A->B->C->D->E->F->G->H->A and
Ashwood got confused and generated an incorrect insertion order
instead of throwing an exception. We fixed the schema and model and
Ashwood cleared right up, so it isn't as urgent for us now (we
deployed a new release of our application on Thursday).
Just thought I'd mention it,
mrg
Re: Ashwood Issues
Posted by Andrus Adamchik <an...@objectstyle.org>.
Very nice. Perhaps one area of Ashwood improvement here would be a better diagnostics of the loops. I.e. if the exception could have the exact relationships involved you could've solved your problem in 5 minutes.
Andrus
On Aug 1, 2011, at 4:13 PM, Michael Gentry wrote:
> BTW Andrus, the algorithm I was using in my entity sorter had a pretty
> significant flaw, so I'm going to have to restart it at some point.
> However, it did help us find a deep DbEntity cycle that was messing
> Ashwood up. We had something like A->B->C->D->E->F->G->H->A and
> Ashwood got confused and generated an incorrect insertion order
> instead of throwing an exception. We fixed the schema and model and
> Ashwood cleared right up, so it isn't as urgent for us now (we
> deployed a new release of our application on Thursday).
>
> Just thought I'd mention it,
>
> mrg
>
Re: Ashwood Issues
Posted by gilbertoca <gi...@gmail.com>.
Michael Gentry-2 wrote:
>
> BTW Andrus, the algorithm I was using in my entity sorter had a pretty
> significant flaw, so I'm going to have to restart it at some point.
> However, it did help us find a deep DbEntity cycle that was messing
> Ashwood up. We had something like A->B->C->D->E->F->G->H->A and
> Ashwood got confused and generated an incorrect insertion order
> instead of throwing an exception. We fixed the schema and model and
> Ashwood cleared right up, so it isn't as urgent for us now (we
> deployed a new release of our application on Thursday).
>
> Just thought I'd mention it,
>
> mrg
>
This framework[1] has some interesting algorithms. Maybe you can see some
useful information there.
Hth,
Gilberto
[1]http://jung.sourceforge.net/index.html
--
View this message in context: http://cayenne.195.n3.nabble.com/Ashwood-Issues-tp3191259p3520383.html
Sent from the Cayenne - Dev mailing list archive at Nabble.com.