When using this kind extended search filter (e.g "(description:<oid_sub_mr>:=\*<assertion>"), the set of matching entries can be erroneous.
all
testcase to be provided
Sometime invalid match
should return only valid match
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 1.3.6.0
<img alt="0001-Ticket-49545-final-substring-extended-filter-search-.patch" src="/389-ds-base/issue/raw/files/cd25da842193662184e758ecd90aabfa3d3253b851e08652eacf397e956b8566-0001-Ticket-49545-final-substring-extended-filter-search-.patch" />
Metadata Update from @tbordaz: - Issue set to the milestone: 1.2.11 (was: 1.3.6.0)
To ssh://pagure.io/389-ds-base.git b831d6a..14ce2fe master -> master To ssh://pagure.io/389-ds-base.git abdde67..e0162a6 389-ds-base-1.3.7 -> 389-ds-base-1.3.7 To ssh://pagure.io/389-ds-base.git 40e9fa1..c127e35 389-ds-base-1.3.6 -> 389-ds-base-1.3.6 To ssh://pagure.io/389-ds-base.git 6fee07c..03a1935 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
Metadata Update from @tbordaz: - Issue assigned to tbordaz
Metadata Update from @tbordaz: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2604
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.