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
