You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (Created) (JIRA)" <ji...@apache.org> on 2012/01/03 17:48:39 UTC

[jira] [Created] (JCR-3198) Broken handling of outer join results over davex

Broken handling of outer join results over davex
------------------------------------------------

                 Key: JCR-3198
                 URL: https://issues.apache.org/jira/browse/JCR-3198
             Project: Jackrabbit Content Repository
          Issue Type: Bug
          Components: jackrabbit-jcr-server, jackrabbit-spi2dav
    Affects Versions: 2.3.6
            Reporter: Jukka Zitting
            Assignee: Jukka Zitting


The davex join support added in JCR-3089 only works correctly when the join returns at least one row and none of the returned rows contain null values for any of the selectors. This should be reasonably straightforward to fix.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (JCR-3198) Broken handling of outer join results over davex

Posted by "Jukka Zitting (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting resolved JCR-3198.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.4

Fixed in revision 1227240 and merged to the 2.4 branch in revision 1227247.
                
> Broken handling of outer join results over davex
> ------------------------------------------------
>
>                 Key: JCR-3198
>                 URL: https://issues.apache.org/jira/browse/JCR-3198
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-jcr-server, jackrabbit-jcr2spi, jackrabbit-spi, jackrabbit-spi2dav
>    Affects Versions: 2.3.6
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>              Labels: davex, join, outer, sql2
>             Fix For: 2.4
>
>
> The davex join support added in JCR-3089 only works correctly when the join returns at least one row and none of the returned rows contain null values for any of the selectors. This should be reasonably straightforward to fix.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (JCR-3198) Broken handling of outer join results over davex

Posted by "Jukka Zitting (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-3198:
-------------------------------

    Component/s: jackrabbit-spi
                 jackrabbit-jcr2spi
    
> Broken handling of outer join results over davex
> ------------------------------------------------
>
>                 Key: JCR-3198
>                 URL: https://issues.apache.org/jira/browse/JCR-3198
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-jcr-server, jackrabbit-jcr2spi, jackrabbit-spi, jackrabbit-spi2dav
>    Affects Versions: 2.3.6
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>              Labels: davex, join, outer, sql2
>             Fix For: 2.4
>
>
> The davex join support added in JCR-3089 only works correctly when the join returns at least one row and none of the returned rows contain null values for any of the selectors. This should be reasonably straightforward to fix.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira