fetch whose fetchspec fits some shared EOs
that unique? That seems surprising.
Thanks a lot and all the best,
OC
>
> From: "o...@ocs.cz <mailto:o...@ocs.cz>" mailto:o...@ocs.cz>>
> Date: Friday, September 28, 2018 at 6:56 PM
> To: Chuck Hill mailto:ch...@gevity
be the first to find this.
Chuck
From: "o...@ocs.cz"
Date: Friday, September 28, 2018 at 6:56 PM
To: Chuck Hill
Cc: WebObjects-Dev Mailing List
Subject: Shared EC woes (was: Flattened one-side M:N fails wildly with SharedEC)
Chuck,
well, so far, I have found two problems with S
Chuck,
well, so far, I have found two problems with SEC. One of them is boringly
self-evident, but a hell to find&fix: very simply, my legacy code did contain
something like
Foo something() {
...
EOUtilities.objectWithPrimaryKeyValue(this.editingContext(),'NonSharedFooEntity',pk)
}
Which,
