There must be something going on here that you are not mentioning. Do you have
multiple EOF stacks (multiple EOObjectStoreCoordinator instances)?
Chuck
> On Jan 12, 2020, at 4:13 PM, OCsite via Webobjects-dev
> wrote:
>
> I think I have probably solved the original problem (quoted below) al
I think I have probably solved the original problem (quoted below) all right,
for the record, by doing essentially this in the
databaseContextWillOrderAdaptorOperations delegate method:
1. go through all the database operations; for each of them
2. go through all the relationships of the DBOp
Chuck,
> On 12 Jan 2020, at 21:01, Chuck Hill wrote:
> It only works for code that does _NSUtilities.classForName(). It only works
> for code that defers knowing the class based on a string.
I see, so it is the dictionary approach after all. I somewhat hoped they might
have tweaked the class
It only works for code that does _NSUtilities.classForName(). It only works
for code that defers knowing the class based on a string.
> On Jan 12, 2020, at 7:00 AM, OCsite via Webobjects-dev
> wrote:
>
> P.S.
>
>> On 12 Jan 2020, at 14:55, OCsite via Webobjects-dev
>> mailto:webobjects-d
P.S.
> On 12 Jan 2020, at 14:55, OCsite via Webobjects-dev
> wrote:
> As for the fixing... well, I guess I can generate the proper AOs myself, but
> the trick is, how do I order them? I would need to reuse the standard default
> ordering which EODatabaseContext does normally; but it does not s
Hello,
I have pursued the problem and it seems to be somewhere at the
EODatabaseOperation level. Implementing the
databaseContextWillOrderAdaptorOperations delegate method and logging this:
===
NSArray databaseContextWillOrderAdaptorOperations(EODatabaseContext dbCtxt,
NSArray databaseOps)
