Apache Directory Project - [jira] Updated: (DIRSERVER-824) Collective attributes are not

This is Interesting: Free IT Magazines  
Home > Archive > Apache Directory Project > January 2007 > [jira] Updated: (DIRSERVER-824) Collective attributes are not





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author [jira] Updated: (DIRSERVER-824) Collective attributes are not
Emmanuel Lecharny (JIRA)

2007-01-25, 1:11 pm


[ https://issues.apache.org/jira/brow...ls:all-tabpanel ]

Emmanuel Lecharny updated DIRSERVER-824:
----------------------------------------

Fix Version/s: 1.5.0

I think this would be better to postpone this issue to 1.5.0 : we don't have real clues on how to fix it quickly in 1.0.1

> Collective attributes are not evaluated in search operations when they are used in filter expressions
> -----------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-824
> URL: https://issues.apache.org/jira/browse/DIRSERVER-824
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.0.1, 1.5.0
> Reporter: Ersin Er
> Fix For: 1.5.0
>
>
> As collective attributes never hit the database, they are not evaluated upon search operations if they are used in filters. This is an hard issue to fix but we may also support this kind of virtual attributes in the future, so we need a way to handle su

ch cases. One solution can be injecting the collective attributes into entries before search operations. Other LDAP servers may be doing this. (I had felt this when I read their documents.) Hoever I am not sure about the negative effects of that way on pe
rformance.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com