rafsun42 commented on code in PR #240: URL: https://github.com/apache/age-website/pull/240#discussion_r1419300088
########## docs/clauses/match.md: ########## @@ -1,20 +1,20 @@ # MATCH -The `MATCH` clause allows you to specify the patterns Cypher will search for in the database. This is the primary way of getting data into the current set of bindings. It is worth reading up more on the specification of the patterns themselves in Patterns. +The `MATCH` clause allows you to specify the patterns a query will search for in the database. This is the primary way of retrieving data for use in a query. -`MATCH` is often coupled to a `WHERE` part which adds restrictions, or predicates, to the `MATCH` patterns, making them more specific. The predicates are part of the pattern description, and should not be considered a filter applied only after the matching is done. This means that `WHERE` should always be put together with the `MATCH` clause it belongs to. + A `WHERE` clause often follows a `MATCH` clause to add user-defined constraints to the matched patterns to manipulate the set of data returned. The constraint predicates are part of the pattern description, and should not be considered a filter applied only after the matching is done. This means that `WHERE` should always be put together with the `MATCH` clause it belongs to. Review Comment: Looks good! Just one thought. Don't we also use the term 'constraint' to refer to database constraints like NOT NULL, DEFAULT etc? 🤔 ########## docs/clauses/match.md: ########## @@ -1,20 +1,20 @@ # MATCH -The `MATCH` clause allows you to specify the patterns Cypher will search for in the database. This is the primary way of getting data into the current set of bindings. It is worth reading up more on the specification of the patterns themselves in Patterns. +The `MATCH` clause allows you to specify the patterns a query will search for in the database. This is the primary way of retrieving data for use in a query. -`MATCH` is often coupled to a `WHERE` part which adds restrictions, or predicates, to the `MATCH` patterns, making them more specific. The predicates are part of the pattern description, and should not be considered a filter applied only after the matching is done. This means that `WHERE` should always be put together with the `MATCH` clause it belongs to. + A `WHERE` clause often follows a `MATCH` clause to add user-defined constraints to the matched patterns to manipulate the set of data returned. The constraint predicates are part of the pattern description, and should not be considered a filter applied only after the matching is done. This means that `WHERE` should always be put together with the `MATCH` clause it belongs to. Review Comment: Looks good! Just one thought. Don't we also use the term 'constraint' to refer to database constraints like NOT NULL, DEFAULT etc? 🤔 -- 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
