[
https://issues.apache.org/jira/browse/JENA-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619128#comment-13619128
]
Rob Vesse commented on JENA-429:
--------------------------------
The problem appears to be down to two factors:
1 - The use of GROUP BY which means the transformation of top level BIND to
project expressions is invalidated
2 - The fact that the generated query (which must come from 2.10.1-SNAPSHOT
because top level BIND would not round trip prior to my recent changes) is sent
to a system using the positively ancient 2.8.8 per the report
I think the version mismatch is less of an issue and that what actually needs
to happen is that top level BINDs are inspected in more detail to determine
whether they should be placed as project expressions or turned into BINDs
> OpAsQuery generating invalid query
> ----------------------------------
>
> Key: JENA-429
> URL: https://issues.apache.org/jira/browse/JENA-429
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Affects Versions: Jena 2.10.0
> Reporter: Andy Seaborne
> Fix For: Jena 2.10.1
>
> Attachments: Jena429_TestCase.java
>
>
> From:
> http://mail-archives.apache.org/mod_mbox/jena-users/201303.mbox/%3CCAFRj_AdcJsJ55xYvqZT7XRiojhNVLuhT8-k8g-0cy5Zk-6T03Q%40mail.gmail.com%3E
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
