davebarnes97 commented on a change in pull request #5844:
URL: https://github.com/apache/geode/pull/5844#discussion_r543781122
##########
File path:
geode-docs/developing/querying_basics/restrictions_and_unsupported_features.html.md.erb
##########
@@ -30,6 +30,6 @@ At a high level, <%=vars.product_name%> does not support the
following querying
- You cannot create an index on fields using Set/List types (Collection
types) that are not comparable. The OQL index implementation expects fields to
be Comparable. To workaround this, you can create a custom Collection type that
implements Comparable.
- ORDER BY is only supported with DISTINCT queries.
-
+- OQL queries aren't pre-validated for references to nonexistent methods and
attributes.
Review comment:
[My suggested revision, adding some of Anil's explanation from the JIRA
comments for context, and expanding contractions to whole words for better
translation/localization. @agingade please review]
In the Geode model, attributes and methods are resolved at runtime during
query execution. This means that OQL queries are not pre-validated for
references to nonexistent methods and attributes.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
