Hi OC,
I see now. Besides the table-renaming-at-SQL-generation idea someone suggested
(which certainly works, I’ve used in the past to hide the complexities of an
old system migrated from many distributed AS400s), there might be support in
your database for something that will get you the same
Fabian,
On 9. 7. 2016, at 12:23, Fabian Peters wrote:
> You can set your own ERXEditingContextDelegate and implement
> editingContextShouldFetchObjects(). There you can access the fetch
> specification and check which entity is being fetched. Then modify the
> qualifier to your liking. I've b
You can set your own ERXEditingContextDelegate and implement
editingContextShouldFetchObjects(). There you can access the fetch
specification and check which entity is being fetched. Then modify the
qualifier to your liking. I've been using this for years in multi-tenant
applications.
To set th
Mark,
On 9. 7. 2016, at 5:23, "Morris, Mark" wrote:
> Just a thought. What about dynamically creating a new EOEntity for each group
> of T_RECORD records represented by a T_TABLE record?
I sort of fear this might bring more problems than those which it would solve.
For one, it would mean each
Chuck,
On 9. 7. 2016, at 6:37, Chuck Hill wrote:
> The answer depends on your definition of “decent”. There is nothing in EOF,
> and nothing that I am aware of in Wonder that will do this.
Meantime I have realised one thing: the "qualifiedRecords" are current-user
(i.e., session) dependent
