[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2152) QueryManager and JCR browser seem to have different view on repository

    [
http://jira.magnolia.info/browse/MAGNOLIA-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17128#action_17128
] 

Gregory Joseph commented on MAGNOLIA-2152:
------------------------------------------

It is likely to be related to indexing. Indexing happens (by default) asynchronously - and queries are
based on those indexes.
Could you post some details about your jackrabbit/oracle configuration ?

> QueryManager and JCR browser seem to have different view on repository
> ----------------------------------------------------------------------
>
>                 Key: MAGNOLIA-2152
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-2152
>             Project: Magnolia
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.5.8
>            Reporter: Philippe Marschall
>            Assignee: Philipp Bracher
>
> We have a very strange issue with querying custom page attributes. We have a custom page dialog that sets
some custom page properties. These attributes are ad hoc and not defined in some sort of schema. We then
have observation code that queries the JCR for pages with these attributes and certain values. Our
queries look like this:
> {code}
> //element(*, mgnl:content) [@someLongAttribute and @someLongAttribute != 0]
> {code}
> {code}
> SELECT *
> FROM mgnl:content
> WHERE someLongAttribute IS NOT NULL AND someLongAttribute != 0
> {code}
> {code}
> //element(*, mgnl:content) [@someBooleanAttribute and @someBooleanAttribute = 'true']
> {code}
> {code}
> SELECT *
> FROM someBooleanAttribute IS NOT NULL AND someBooleanAttribute = 'true'
> {code}
> The behavior we are observing is that for certain pages the check for an attribute value is always false
even if it should match according to the JCR browser. However the check for the attribute presence works as
expected. As soon as we change a page attribute in the JCR browser the checks for the values work even if
changed with the page properties dialog.
> This issue is very rare and we have not yet found a way to reproduce or trigger it.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------