Hiya,
Going totally off memory here from years back. The search engine was
designed to expand the scope that aliases introduce with their
references. Meaning the scope expands to new areas if the reference
points outside of the base of the search: of course this is more
complex when considering deref modes and where the alias is.
But essentially I was under the impression that dereferencing was not
handled in higher levels outside of the xdbm search in the partition.
Hence not in the filters injected into the returned cursor system. Are
u witnessing the contrary conditions?
Sent from my iPhone
On Jun 16, 2011, at 12:21 PM, Emmanuel Lecharny <[email protected]>
wrote:
Hi,
so I slept on the problem, and here are a few thoughts I had this
morning :
- first, the alias handling can't be done in the doSimpleSearch() as
I thought, because if we do so, alias dereferencing won't be handled
when using the coreSession. It must be handled by the
EntryFilteringCursor. Remains to see how to implement that there.
- second, we may have some issue when an alias points to a non
existing entry. What will the cursor.next() return in this case ?
The alias exists, so the cursor.next() will move forward, to
something that does not exist (this is a Pierre-Arnaud thought).
- third, we have to fix the reverter, which doe snot handle
correctly alias removal, if the entry which is pointed doe snot
exist anymore. There is a JIRA for that issue.
I'll do my best today to get something done.
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
