Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

highlight properties limited to be used in yield(rather than in WHERE for now) #1306

Closed
1 task
wey-gu opened this issue Dec 7, 2021 · 7 comments
Closed
1 task
Assignees

Comments

@wey-gu
Copy link
Contributor

wey-gu commented Dec 7, 2021

This should be highlighted before the next release.

  • en doc lift
@wey-gu
Copy link
Contributor Author

wey-gu commented Dec 7, 2021

@wey-gu
Copy link
Contributor Author

wey-gu commented Dec 7, 2021

Just noticed that we have examples of using properties in GO/LOOKUP queries, we should consider reverting them in the 2.6.1 branch.

@cooper-lzy
Copy link
Contributor

These problems are in the document, but the WHERE clause in the GO statement can use properties. Maybe this is a bug?

image
image

@wey-gu
Copy link
Contributor Author

wey-gu commented Dec 7, 2021

@nevermore3 could you please kindly help clarify that the limitation in 2.6.1 that properties() cannot be used in where clause applies to MATCH only, that is, it's already supported on GO/LOOKUP expressions?

@cooper-lzy
Copy link
Contributor

Consult the developer to confirm that the above problem is an unexpected situation, and we will change the documentation.

@wey-gu
Copy link
Contributor Author

wey-gu commented Dec 7, 2021

Consult the developer to confirm that the above problem is an unexpected situation, and we will change the documentation.

Got it, thanks @cooper-lzy!

@cooper-lzy
Copy link
Contributor

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants