You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Daniel Kuppitz (JIRA)" <ji...@apache.org> on 2015/04/07 17:44:12 UTC

[jira] [Commented] (TINKERPOP3-601) Consider to get rid of .back()

    [ https://issues.apache.org/jira/browse/TINKERPOP3-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14483388#comment-14483388 ] 

Daniel Kuppitz commented on TINKERPOP3-601:
-------------------------------------------

I wouldn't care if we simply get rid of {{.back()}}.

{code:none}
gremlin> g.V(1).out().as("x").out().as("x").select("x")
==>v[5]
==>v[3]
{code}

This is what Matt wants and what the current behavior is. Nobody else stood up to say that this is an unexpected behavior. Thus, in short: no changes in {{.select()}} necessary.

> Consider to get rid of .back()
> ------------------------------
>
>                 Key: TINKERPOP3-601
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-601
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: process
>            Reporter: Daniel Kuppitz
>            Assignee: Daniel Kuppitz
>             Fix For: 3.0.0.GA
>
>
> Consider to get rid of {{.back()}} in favor of {{.select()}}. There's a discussion on the mailing list that points out differences in the behavior of both steps, which should be taken into account since some people may rely on those differences.
> https://groups.google.com/d/msg/gremlin-users/UnYK2lzXlkA/1IF4nZ__D9AJ



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)