| Hi there,
hunting for an unrelated bug, I have noticed I've got an EODatabaseContext, not ERXDatabaseContext. Checking the Wonder sources it looks like it is opt-in and (along with EODatabase) will not load unless er.extensions.ERXDatabaseContext.activate (or remote synchroniser) is set.
I wonder why? The source seems not to be remote-sync-specific, far as I can say; EODatabaseContext fixes some problem with a single-table inheritance, thus it would seem prudent to have it all the time, or, at the very least, by default with an opt-out if someone does not want to.
As for EODatabase, I admit I do not quite get the point of its snapshot cache (is the thing documented anywhere? This document really does not say much), that one well might be remote-sync-specific for all I know.
What is the reason these extensions are not normally used, unless the user explicitly asks for them? Is there some danger or another drawback caused by using them?
Thanks, OC
|