jrgemignani commented on issue #1461:
URL: https://github.com/apache/age/issues/1461#issuecomment-1898888915
@MuhammadTahaNaveed I feel like this could be argued either way, if I
understand the question.
When someone is looking for, SELECT or MATCH, they're asking if something
has this something. It could be, does it have it or does it equal it. But, it
ends up being a bit ambiguous as to what is wanted.
Maybe we should have a default behavior, say contains, and an operator to
modify that behavior?
For example,
Contains as default, equals when specified -
```
MATCH (x:Customer {school: {name: 'XYZ College'}}) return x
MATCH (x:Customer ={school: {name: 'XYZ College'}}) return x
```
Equals as default, contains when specified -
```
MATCH (x:Customer {school: {name: 'XYZ College'}}) return x
MATCH (x:Customer ~{school: {name: 'XYZ College'}}) return x
```
I say a default **contains** because it feels like when doing a **SELECT**
or **MATCH** you are asking for all occurrences and then, by using qualifiers,
you are narrowing the results down.
Just my thoughts
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@age.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
