-
Improvement
-
Resolution: Fixed
-
Neutral
-
6.2.27
-
None
-
None
-
Empty show more show less
-
Yes
-
Nucleus 29
-
2
Steps to reproduce
- Go to https://nightly.magnolia-cms.com/.magnolia/admincentral#app:pages-app:browser
- Filter via page template dropdown
- Inspect/debug the constructed JCR query performance/timing
Expected results
SELECT * FROM [nt:base] AS t WHERE ISDESCENDANTNODE(t, [/]) AND t.[jcr:primaryType] = 'mgnl:page' AND LOWER(t.[mgnl:template]) = 'mtk2:pages/basic' AND LOWER(t.title) LIKE '%test%' AND LOWER(LOCALNAME(t)) LIKE '%test%'
Actual results
SELECT * FROM [nt:base] AS t WHERE ISDESCENDANTNODE(t, [/]) AND t.[jcr:primaryType] = 'mgnl:page' AND LOWER(t.[mgnl:template]) LIKE '%mtk2:pages/basic%' AND LOWER(t.title) LIKE '%test%' AND LOWER(LOCALNAME(t)) LIKE '%test%'
Workaround
Development notes
JcrQueryBuilder doesn't know about the source field (was it textField or a comboBoxField) but one can assume any system property (prefixed with mgnl:) should be search by equality, therefore the usage of LIKE is redundant.
Acceptance criteria
- is causing
-
MGNLUI-8573 App column filtering by mgnl:lastModifiedBy doesn't return any results for partial matches
- Open
- split from
-
MAGNOLIA-8347 JcrQueryBuilder performance issues.
- Closed
1.
|
Implementation | Completed | Antonín Juran | |||||||||
2.
|
Code review | Completed | Sang Ngo Huu |
|
||||||||
3.
|
Pre-integration QA | Completed | Sang Ngo Huu |
|
||||||||
4.
|
Final QA | Completed | Jaromir Sarf |