Le 12/11/12 2:09 PM, Kiran Ayyagari a écrit :
On Tue, Dec 11, 2012 at 4:11 PM, Emmanuel Lécharny elecha...@gmail.comwrote:
Le 12/11/12 11:02 AM, Kiran Ayyagari a écrit :
On Tue, Dec 11, 2012 at 3:23 PM, Emmanuel Lécharny elecha...@gmail.com
wrote:
But, and there is a big but, when
On Thu, Dec 13, 2012 at 2:31 PM, Emmanuel Lécharny elecha...@gmail.comwrote:
Le 12/11/12 2:09 PM, Kiran Ayyagari a écrit :
On Tue, Dec 11, 2012 at 4:11 PM, Emmanuel Lécharny elecha...@gmail.com
wrote:
Le 12/11/12 11:02 AM, Kiran Ayyagari a écrit :
On Tue, Dec 11, 2012 at 3:23 PM,
Hi !
I spent some time those past two days checking the way we are processing
the filtering of attributes when doing a search or a lookup. A new
OperationContext class has been created to merge the common elements
from the lookup, search and list operation. So far, so good.
Still, while adding
On Tue, Dec 11, 2012 at 3:23 PM, Emmanuel Lécharny elecha...@gmail.comwrote:
Hi !
I spent some time those past two days checking the way we are processing
the filtering of attributes when doing a search or a lookup. A new
OperationContext class has been created to merge the common elements
Le 12/11/12 11:02 AM, Kiran Ayyagari a écrit :
On Tue, Dec 11, 2012 at 3:23 PM, Emmanuel Lécharny elecha...@gmail.comwrote:
But, and there is a big but, when processing a search request, we do a
direct lookup from the backend, and we are not going through this chain.
What happens is that we
On Tue, Dec 11, 2012 at 4:11 PM, Emmanuel Lécharny elecha...@gmail.comwrote:
Le 12/11/12 11:02 AM, Kiran Ayyagari a écrit :
On Tue, Dec 11, 2012 at 3:23 PM, Emmanuel Lécharny elecha...@gmail.com
wrote:
But, and there is a big but, when processing a search request, we do a
direct lookup
