Skip to content

weird behavior with SELECT #51

Closed Answered by tobiemh
ehsanonline asked this question in Q&A
Discussion options

You must be logged in to vote

Hi @ehsanonline thanks for starting this discussion!

Two different things here:

  1. Subsequent SELECT fields will always replace previous ones. So if you run SELECT *, <-write.in, <-write FROM article:surreal; then the last <-write field will overwrite the previous one. There is a way of getting round this. You could write something like the following:
SELECT *, <-write.in AS first, <-write AS second FROM article:surreal;

However there is a better way of doing this, which only traverses once:

SELECT *, <-(write AS first)<-(user AS second) FROM article:surreal;
  1. We're looking to add a DISTINCT keyword into the graph traversal, so that it only pulls out distinct edges. Would be great to get y…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@ehsanonline
Comment options

Answer selected by ehsanonline
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants