There are some EODatabaseContext.Delegate methods that might do what you want,
but they will affect all Ecs, not just the temp one.
Chuck
On 2015-02-14, 3:34 AM, "OC" wrote:
Hello there,
another possible way of optimization would be if I did not refetch _all_
objects touched, but only those w
Hi,
On 2015-02-13, 11:34 PM, "OC" wrote:
Hello there,
I have bumped into a bottleneck in some pretty ancient parts of my code, and am
seeking an advice how to fix it. The bottleneck is caused by
sorting-and-searching objects of 1:N relationships:
=== my EO code ===
public NSArray orderedP
Hi,
This code makes no sense to me. One of us is confused. Given how today has
been going it might be me. Confusion below
On 2015-02-14, 1:59 AM, "OC" wrote:
P.S.
On 14. 2. 2015, at 8:34, OC mailto:o...@ocs.cz>> wrote:
I tried to cache the object's permanentGlobalID when found or added new
Ken,
On 14. 2. 2015, at 16:04, Ken Anderson wrote:
> This is certainly odd behavior - something else must be going on.
>
> In your example (a) will always happen - EOF will fault in relationships
> before adding objects to them. But, once that relationship is there, it
> should stay in that
This is certainly odd behavior - something else must be going on.
In your example (a) will always happen - EOF will fault in relationships before
adding objects to them. But, once that relationship is there, it should stay
in that EO until some kind of invalidation happens.
Any chance you coul
Hello there,
as Alice said, it gets couriouser and couriouser. I am now logging SQL, and --
at least to me -- it seems my application is SELECTing way too often.
The code is still related to the price offers of my previous posts; this time
though I am using the default EC and I am not setting f
Hello there,
another possible way of optimization would be if I did not refetch _all_
objects touched, but only those which do need a refetch.
Means, when saving important data which can be changed anytime by another
thread or instance, I exploit the pattern
===
EOObjectStore osc=ec.rootObject
P.S.
On 14. 2. 2015, at 8:34, OC wrote:
> I tried to cache the object's permanentGlobalID when found or added new valid
> one ... it still does not work well
Actually it seems I must be misunderstanding somehow the behaviour of global
IDs, worth to ask for an advice what I am doing wrong.
I c
