You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@geode.apache.org by db...@apache.org on 2021/01/04 17:20:38 UTC
[geode] branch develop updated: GEODE-7802: Add disclaimer for OQL
queries in UG (#5844)
This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/geode.git
The following commit(s) were added to refs/heads/develop by this push:
new 93f8000 GEODE-7802: Add disclaimer for OQL queries in UG (#5844)
93f8000 is described below
commit 93f80004390bea40764db7e669e0ca4604fbfefa
Author: Jakov Varenina <62...@users.noreply.github.com>
AuthorDate: Mon Jan 4 18:19:21 2021 +0100
GEODE-7802: Add disclaimer for OQL queries in UG (#5844)
* GEODE-7802: Add disclaimer in UG: OQL queries are not pre-validated for nonexistent attributes
and methods
---
.../querying_basics/restrictions_and_unsupported_features.html.md.erb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/geode-docs/developing/querying_basics/restrictions_and_unsupported_features.html.md.erb b/geode-docs/developing/querying_basics/restrictions_and_unsupported_features.html.md.erb
index 0927a04..d4a826e 100644
--- a/geode-docs/developing/querying_basics/restrictions_and_unsupported_features.html.md.erb
+++ b/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.
-
+- 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.
In addition, there are some specific limitations on partitioned region querying. See [Partitioned Region Query Restrictions](../query_additional/partitioned_region_query_restrictions.html#concept_5353476380D44CC1A7F586E5AE1CE7E8).