Re: D2W: QueryAllPage?
Re: D2W: QueryAllPage?
- Subject: Re: D2W: QueryAllPage?
- From: Ashley Aitken <email@hidden>
- Date: Fri, 23 Apr 2004 21:55:03 +0800
On 23/04/2004, at 9:30 PM, Anjo Krank wrote:
Am 23.04.2004 um 15:04 schrieb Ashley Aitken:
The problem is, how can I do this with a QueryAllPage? I would
basically like to hang an auxilliary qualifier onto each of the
separate entity sub-queries? I believe it would need to be different
for each entity.
Is there any easy way to do this, or do I need to setup a
nextPageDelegate for each of the different entity sub-queries as I
suggested above for single entity QueryPage.
Has anyone done this? Any suggestions or ideas?
Sure: use the "visibleEntityNames" key with the ERNEUQueryAllPage.
No sorry, I probably didn't explain it clearly enough. I do use
visibleEntityNames to hide some entities, but now when the user
searches in a visible entity I only want them to find those items that
are related to them (how they are related will depend on the entity,
e.g. directly or indirectly related).
By default, I believe the EODataSource for each of the entities in the
QueryAllPage is just the EODatabaseDataSource for that Entity (ie all
the rows in that table). I need to hang an auxiliary qualifier onto
each visible entity.
As I mentioned in the original post, I can do this (I think) for
separate query pages, but I would like to do it for the QueryAllPage -
this page represents sort of a "quick find" page that I think is useful
separate from the single entity query pages.
I am thinking of providing something like a nextPage delegates for each
of the actions (two per entity) but this could be quite a bit of work
as one of the actions has the query already built and the other
provides a query page etc.
I considered using the "filter button" from Project WONDER attached to
a list page but that, I believe, requires that all the objects have
been fetched, which sort of negates the purpose of doing a search (ie
to find a few objects amongst a large number of objects).
I need something like "restrictChoices" but for a query (eg
restrictFetch)?
Or some rule like:
(task like 'query*') and (entity.name = 'Entity1')
=>
auxiliaryQualifier = ...
Cheers,
Ashley.
--
Ashley Aitken
Perth, Western Australia
mrhatken at mac dot com
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.