[
https://issues.apache.org/jira/browse/TINKERPOP3-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14740928#comment-14740928
]
Matt Frantz commented on TINKERPOP3-837:
----------------------------------------
The SQL precedent is relevant, as it sets expectations for database-like API's.
I guess the decision concerns both "which features should we bundle in {{P}}?"
and "what should they be called?" And there is also "should we make a breaking
change?" For example, we could change {{between}} as you suggest, but add
{{interval}} or {{halfOpenInterval}} for the current behavior. Or we could
overload {{between}} as you suggest. Overloading seems to be the preference in
the Gremlin design in other contexts, but I'm not sure we need to apply the
same rules of economy with {{P}} as we do with step names.
> Make P.between symmetrical
> --------------------------
>
> Key: TINKERPOP3-837
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-837
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.0.1-incubating
> Reporter: pieter martin
> Assignee: Marko A. Rodriguez
>
> {{P.between}} implements {{Compare.gte}} and {{Compare.lt}}
> This is asymmetrical and counter intuitive.
> Can we change it to be {{Compare.gt}} and {{Compare.lt}} or
> {{Compare.gte}} and {{Compare.lte}}
> Either inclusive or exclusive but not asymmetrical as it is now.
> I would vote for exclusive as it is arguably close to the English meaning of
> between.
> According to Daniel on the forum this was done for historical pragmatic
> reasons via Matthias and the old {{.interval()}} step.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
