Re: Looking for strategy

[Philippe Rabier]

Hi Markus,

I made a presentation 
http://www.slideshare.net/wocommunity/filtering-data-with-d2w

It could help you as well. 

Our need was to manage a multi-tenants database so it was close of your 
description: a user belongs to a company and can see only the data linked to 
the company. 

Best,

Philippe

> On 22 juil. 2016, at 09:49, Chuck Hill  wrote:
> 
> EOEditingContext.Delegate.editingContextShouldFetchObjects is what I was 
> going to suggest too.  Get the session to stash the region details in a 
> thread local in awake and remove in sleep.
>  
> I think it was OC that tried this before, but he wanted it to also affect 
> firing a to-many relationship fault, IIRC.
>  
> From:  <mailto:webobjects-dev-bounces+chill=gevityinc@lists.apple.com>> on 
> behalf of Ramsey Gurley  <mailto:rgur...@smarthealth.com>>
> Date: Friday, July 22, 2016 at 9:43 AM
> To: Markus Ruggiero  <mailto:mailingli...@kataputt.com>>
> Cc: "webobjects-dev@lists.apple.com <mailto:webobjects-dev@lists.apple.com>" 
> mailto:webobjects-dev@lists.apple.com>>
> Subject: Re: Looking for strategy
>  
> This may be possible using 
> EOEditingContext.Delegate.editingContextShouldFetchObjects to modify fetch 
> specs in flight. I vaguely remember someone saying they tried that and it 
> didn’t work out.
>  
> If it isn’t possible there, then perhaps it would be possible to produce an 
> EC subclass that appends the proper qualifier to fetches in 
> objectsWithFetchSpecification, then ERXEC.setFactory to produce your subclass 
> when the application starts.
>  
> You’ll probably need QualifierTraversal, ERDQualifierTraversal, or 
> ERXQualifierTraversal for qualifier modifications, since the qualifier you 
> need to modify might be deeply nested. Keeping track of which entity the 
> attribute key applies to might be difficult since the qualifier has no link 
> to it.
>  
> On Jul 22, 2016, at 7:27 AM, Markus Ruggiero  <mailto:mailingli...@kataputt.com>> wrote:
>  
> Hi Theodore,
> thanks for the tip, will look into it. However I do have some non-D2W 
> queries, primarily related to direct action batch processing and things. 
> There I'd have to not forget to add the Region query criteria in code 
> everywhere today (and tomorrow, and also tell my co-workers). The D2W 
> approach is great as it is kind of global (at least in D2W space). Even more 
> global would be someting I could plug into the lower levels of EOF that would 
> add the criteria unconditionally, no matter D2W or "handcrafted" fetch spec.
> ---markus---
> On 22.07.2016, at 15:57, Theodore Petrosky  <mailto:tedp...@yahoo.com>> wrote:
> Does the ERDQueryDataSourceDelegateInterface help you here?
> https://wiki.wocommunity.org/display/documentation/D2W+Flow+Control 
> <https://wiki.wocommunity.org/display/documentation/D2W+Flow+Control>
> On Jul 22, 2016, at 9:43 AM, Markus Ruggiero  <mailto:mailingli...@kataputt.com>> wrote:
> Folks,
> My app has some 50+ entities. About 2 third of them have data that is 
> specfiic to a Region, the rest of the entities is Region agnostic.
> Example:
> Article toMany Descriptions
> Article is Region agnostic but can have Region specific descriptions, thus 
> Descriptions have an optional toOne to Region
> Background: A user of the app is assigned a Region during login. He must be 
> allowed to only see Region agnostic data or objects that are assigned to the 
> current Region only.
> What I want is a generic way to have something like the following SQL 
> generated by the Frameworks:
> select * from article where some_selection_criteria;  -- no region reference
> select * from description where some_selection_criteria (AND REGION_ID IS 
> NULL OR REGION_ID = A_GIVEN_REGION_ID);
> This must also function for queries like: select all articles that have 
> description for region XYZ.
> I am thinking along the following lines: attach some code deep in the 
> framework to add such a restricting clause to where for every select for any 
> region specific table.
> How would I do this? Any better ideas?
> Thanks a lot
> ---markus---
> ___
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com 
> <mailto:Webobjects-dev@lists.apple.com>)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com 
> <https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com>
> This email sent to tedp...@yahoo.com <mailto:tedp...@yahoo.com>
> ___
> Do not po

Re: Looking for strategy

[Chuck Hill]

EOEditingContext.Delegate.editingContextShouldFetchObjects is what I was going 
to suggest too.  Get the session to stash the region details in a thread local 
in awake and remove in sleep.

I think it was OC that tried this before, but he wanted it to also affect 
firing a to-many relationship fault, IIRC.

From:  on behalf of 
Ramsey Gurley 
Date: Friday, July 22, 2016 at 9:43 AM
To: Markus Ruggiero 
Cc: "webobjects-dev@lists.apple.com" 
Subject: Re: Looking for strategy

This may be possible using 
EOEditingContext.Delegate.editingContextShouldFetchObjects to modify fetch 
specs in flight. I vaguely remember someone saying they tried that and it 
didn’t work out.

If it isn’t possible there, then perhaps it would be possible to produce an EC 
subclass that appends the proper qualifier to fetches in 
objectsWithFetchSpecification, then ERXEC.setFactory to produce your subclass 
when the application starts.

You’ll probably need QualifierTraversal, ERDQualifierTraversal, or 
ERXQualifierTraversal for qualifier modifications, since the qualifier you need 
to modify might be deeply nested. Keeping track of which entity the attribute 
key applies to might be difficult since the qualifier has no link to it.

On Jul 22, 2016, at 7:27 AM, Markus Ruggiero 
mailto:mailingli...@kataputt.com>> wrote:

Hi Theodore,
thanks for the tip, will look into it. However I do have some non-D2W queries, 
primarily related to direct action batch processing and things. There I'd have 
to not forget to add the Region query criteria in code everywhere today (and 
tomorrow, and also tell my co-workers). The D2W approach is great as it is kind 
of global (at least in D2W space). Even more global would be someting I could 
plug into the lower levels of EOF that would add the criteria unconditionally, 
no matter D2W or "handcrafted" fetch spec.
---markus---
On 22.07.2016, at 15:57, Theodore Petrosky 
mailto:tedp...@yahoo.com>> wrote:
Does the ERDQueryDataSourceDelegateInterface help you here?
https://wiki.wocommunity.org/display/documentation/D2W+Flow+Control
On Jul 22, 2016, at 9:43 AM, Markus Ruggiero 
mailto:mailingli...@kataputt.com>> wrote:
Folks,
My app has some 50+ entities. About 2 third of them have data that is specfiic 
to a Region, the rest of the entities is Region agnostic.
Example:
Article toMany Descriptions
Article is Region agnostic but can have Region specific descriptions, thus 
Descriptions have an optional toOne to Region
Background: A user of the app is assigned a Region during login. He must be 
allowed to only see Region agnostic data or objects that are assigned to the 
current Region only.
What I want is a generic way to have something like the following SQL generated 
by the Frameworks:
select * from article where some_selection_criteria;  -- no region reference
select * from description where some_selection_criteria (AND REGION_ID IS NULL 
OR REGION_ID = A_GIVEN_REGION_ID);
This must also function for queries like: select all articles that have 
description for region XYZ.
I am thinking along the following lines: attach some code deep in the framework 
to add such a restricting clause to where for every select for any region 
specific table.
How would I do this? Any better ideas?
Thanks a lot
---markus---
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  
(Webobjects-dev@lists.apple.com<mailto:Webobjects-dev@lists.apple.com>)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com
This email sent to tedp...@yahoo.com<mailto:tedp...@yahoo.com>
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  
(Webobjects-dev@lists.apple.com<mailto:Webobjects-dev@lists.apple.com>)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/rgurley%40smarthealth.com
This email sent to rgur...@smarthealth.com<mailto:rgur...@smarthealth.com>


___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  
(Webobjects-dev@lists.apple.com<mailto:Webobjects-dev@lists.apple.com>)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/chill%40gevityinc.com

This email sent to ch...@gevityinc.com<mailto:ch...@gevityinc.com>
 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Looking for strategy

[Ramsey Gurley]

This may be possible using 
EOEditingContext.Delegate.editingContextShouldFetchObjects to modify fetch 
specs in flight. I vaguely remember someone saying they tried that and it 
didn’t work out. 

If it isn’t possible there, then perhaps it would be possible to produce an EC 
subclass that appends the proper qualifier to fetches in 
objectsWithFetchSpecification, then ERXEC.setFactory to produce your subclass 
when the application starts.

You’ll probably need QualifierTraversal, ERDQualifierTraversal, or 
ERXQualifierTraversal for qualifier modifications, since the qualifier you need 
to modify might be deeply nested. Keeping track of which entity the attribute 
key applies to might be difficult since the qualifier has no link to it.

On Jul 22, 2016, at 7:27 AM, Markus Ruggiero  wrote:

> Hi Theodore,
> 
> thanks for the tip, will look into it. However I do have some non-D2W 
> queries, primarily related to direct action batch processing and things. 
> There I'd have to not forget to add the Region query criteria in code 
> everywhere today (and tomorrow, and also tell my co-workers). The D2W 
> approach is great as it is kind of global (at least in D2W space). Even more 
> global would be someting I could plug into the lower levels of EOF that would 
> add the criteria unconditionally, no matter D2W or "handcrafted" fetch spec.
> 
> 
> ---markus---
> 
> 
> 
> 
>> On 22.07.2016, at 15:57, Theodore Petrosky  wrote:
>> 
>> Does the ERDQueryDataSourceDelegateInterface help you here?
>> 
>> https://wiki.wocommunity.org/display/documentation/D2W+Flow+Control
>> 
>> 
>>> On Jul 22, 2016, at 9:43 AM, Markus Ruggiero  
>>> wrote:
>>> 
>>> Folks,
>>> 
>>> My app has some 50+ entities. About 2 third of them have data that is 
>>> specfiic to a Region, the rest of the entities is Region agnostic.
>>> 
>>> Example:
>>> Article toMany Descriptions
>>> Article is Region agnostic but can have Region specific descriptions, thus 
>>> Descriptions have an optional toOne to Region
>>> 
>>> Background: A user of the app is assigned a Region during login. He must be 
>>> allowed to only see Region agnostic data or objects that are assigned to 
>>> the current Region only.
>>> 
>>> What I want is a generic way to have something like the following SQL 
>>> generated by the Frameworks:
>>> 
>>> select * from article where some_selection_criteria;  -- no region reference
>>> select * from description where some_selection_criteria (AND REGION_ID IS 
>>> NULL OR REGION_ID = A_GIVEN_REGION_ID);
>>> 
>>> This must also function for queries like: select all articles that have 
>>> description for region XYZ.
>>> 
>>> I am thinking along the following lines: attach some code deep in the 
>>> framework to add such a restricting clause to where for every select for 
>>> any region specific table.
>>> 
>>> How would I do this? Any better ideas?
>>> 
>>> Thanks a lot
>>> ---markus---
>>> 
>>> 
>>> 
>>> ___
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
>>> Help/Unsubscribe/Update your Subscription:
>>> https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com
>>> 
>>> This email sent to tedp...@yahoo.com
>> 
> 
> ___
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/rgurley%40smarthealth.com
> 
> This email sent to rgur...@smarthealth.com


 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Looking for strategy

[Markus Ruggiero]

Hi Theodore,

thanks for the tip, will look into it. However I do have some non-D2W queries, 
primarily related to direct action batch processing and things. There I'd have 
to not forget to add the Region query criteria in code everywhere today (and 
tomorrow, and also tell my co-workers). The D2W approach is great as it is kind 
of global (at least in D2W space). Even more global would be someting I could 
plug into the lower levels of EOF that would add the criteria unconditionally, 
no matter D2W or "handcrafted" fetch spec.


---markus---




> On 22.07.2016, at 15:57, Theodore Petrosky  wrote:
> 
> Does the ERDQueryDataSourceDelegateInterface help you here?
> 
> https://wiki.wocommunity.org/display/documentation/D2W+Flow+Control 
> 
> 
> 
>> On Jul 22, 2016, at 9:43 AM, Markus Ruggiero > > wrote:
>> 
>> Folks,
>> 
>> My app has some 50+ entities. About 2 third of them have data that is 
>> specfiic to a Region, the rest of the entities is Region agnostic.
>> 
>> Example:
>> Article toMany Descriptions
>> Article is Region agnostic but can have Region specific descriptions, thus 
>> Descriptions have an optional toOne to Region
>> 
>> Background: A user of the app is assigned a Region during login. He must be 
>> allowed to only see Region agnostic data or objects that are assigned to the 
>> current Region only.
>> 
>> What I want is a generic way to have something like the following SQL 
>> generated by the Frameworks:
>> 
>> select * from article where some_selection_criteria;  -- no region reference
>> select * from description where some_selection_criteria (AND REGION_ID IS 
>> NULL OR REGION_ID = A_GIVEN_REGION_ID);
>> 
>> This must also function for queries like: select all articles that have 
>> description for region XYZ.
>> 
>> I am thinking along the following lines: attach some code deep in the 
>> framework to add such a restricting clause to where for every select for any 
>> region specific table.
>> 
>> How would I do this? Any better ideas?
>> 
>> Thanks a lot
>> ---markus---
>> 
>> 
>> 
>> ___
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com 
>> )
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com 
>> 
>> 
>> This email sent to tedp...@yahoo.com
> 

 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Looking for strategy

[Theodore Petrosky]

Does the ERDQueryDataSourceDelegateInterface help you here?

https://wiki.wocommunity.org/display/documentation/D2W+Flow+Control 



> On Jul 22, 2016, at 9:43 AM, Markus Ruggiero  
> wrote:
> 
> Folks,
> 
> My app has some 50+ entities. About 2 third of them have data that is 
> specfiic to a Region, the rest of the entities is Region agnostic.
> 
> Example:
> Article toMany Descriptions
> Article is Region agnostic but can have Region specific descriptions, thus 
> Descriptions have an optional toOne to Region
> 
> Background: A user of the app is assigned a Region during login. He must be 
> allowed to only see Region agnostic data or objects that are assigned to the 
> current Region only.
> 
> What I want is a generic way to have something like the following SQL 
> generated by the Frameworks:
> 
> select * from article where some_selection_criteria;  -- no region reference
> select * from description where some_selection_criteria (AND REGION_ID IS 
> NULL OR REGION_ID = A_GIVEN_REGION_ID);
> 
> This must also function for queries like: select all articles that have 
> description for region XYZ.
> 
> I am thinking along the following lines: attach some code deep in the 
> framework to add such a restricting clause to where for every select for any 
> region specific table.
> 
> How would I do this? Any better ideas?
> 
> Thanks a lot
> ---markus---
> 
> 
> 
> ___
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com
> 
> This email sent to tedp...@yahoo.com

 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Looking for strategy

[Markus Ruggiero]

Folks,

My app has some 50+ entities. About 2 third of them have data that is specfiic 
to a Region, the rest of the entities is Region agnostic.

Example:
Article toMany Descriptions
Article is Region agnostic but can have Region specific descriptions, thus 
Descriptions have an optional toOne to Region

Background: A user of the app is assigned a Region during login. He must be 
allowed to only see Region agnostic data or objects that are assigned to the 
current Region only.

What I want is a generic way to have something like the following SQL generated 
by the Frameworks:

select * from article where some_selection_criteria;  -- no region reference
select * from description where some_selection_criteria (AND REGION_ID IS NULL 
OR REGION_ID = A_GIVEN_REGION_ID);

This must also function for queries like: select all articles that have 
description for region XYZ.

I am thinking along the following lines: attach some code deep in the framework 
to add such a restricting clause to where for every select for any region 
specific table.

How would I do this? Any better ideas?

Thanks a lot
---markus---



 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com