The problem with this solution is that you must wake up every object
found, thus negating the performance/memory advantaged of ZCatalog's
lazy result sets.
Since you said (in your other message) that the restriction is by role,
couldn't you just index the roles allowed to view a given object a
Hi all,
in case someone have same problem as me (see "ZCatalog - hiding query
results" thread for more info) - I got a solution:
- create a product that subclasses ZCatalog
- in this product overwrite ZCatalog.getobject with
def getobject(self, rid):
"""foo"""
obj = self.aq_parent
On Fri, 16 Nov 2001 13:19:20 + Steve Alexander <[EMAIL PROTECTED]>
wrote:
>> Now your users see only those hits in a query which apply to objects
>> they are allowed to "View".
>
>
>However, you will be loading each object that is a potential query
>result into memory for every query. That c
Igor Stroh wrote:
>
> Now your users see only those hits in a query which apply to objects they
> are allowed to "View".
However, you will be loading each object that is a potential query
result into memory for every query. That could be a lot of objects.
--
Steve Alexander
Software Engineer
Hi all,
in case someone have same problem as me (see "ZCatalog - hiding query
results" thread for more info) - I got a solution:
- create a product that subclasses ZCatalog
- in this product overwrite ZCatalog.getobject with
def getobject(self, rid):
"""foo"""
obj = self.aq_parent
