[
https://issues.apache.org/jira/browse/JENA-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14599572#comment-14599572
]
Andy Seaborne commented on JENA-973:
------------------------------------
The fix is to add {{Expr.equalsBySyntax}} in addition to {{.equals}}.
{{hashCode}} is unaffected and implement that in the {{Expr}} subsystem. While
a rather wider ranging change, even though internal, this put the codebase on a
solid long term footing for any SPARQL syntax manipulation.
Custom filter functions are not invalidated.
> Expression NOT EXISTS define equality by alegbra equivalence, not syntax
> equivalance.
> -------------------------------------------------------------------------------------
>
> Key: JENA-973
> URL: https://issues.apache.org/jira/browse/JENA-973
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Affects Versions: Jena 2.13.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Minor
>
> {{FILTER NOT EXISTS}} (and {{FILTER EXISTS}}) define their {{.equals}} by the
> equality of the algebra expression of the pattern part. This works except
> they are also syntax elements. There can be two different syntax ways to
> write what becomes the same algebra (but not the other way round).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
