[
https://issues.apache.org/jira/browse/GEODE-7802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17249063#comment-17249063
]
Anilkumar Gingade commented on GEODE-7802:
------------------------------------------
I don't understand this requirement.
Even in case of other RDBMS query language, the existence of columns are
determined either during query-compilation or query-execution time; and also
for complex queries it can only determine the existence during execution time;
that is what GEODE OQL engine is doing.
One thing that could help to call out is; OQL query engine determines the field
or methods on the object during query execution time.
> User Guide - add disclaimer that OQL queries are not pre-validated for
> nonexistent attributes
> ---------------------------------------------------------------------------------------------
>
> Key: GEODE-7802
> URL: https://issues.apache.org/jira/browse/GEODE-7802
> Project: Geode
> Issue Type: Improvement
> Components: docs
> Reporter: Dave Barnes
> Priority: Minor
> Labels: pull-request-available
>
> Community member @deepak khopade requests that we add a disclaimer to the
> user guide stating that OQL queries are not pre-screened for references to
> nonexistent attributes. The assertion is that users who have experience with
> other query models may expect Geode to apply such validation. In the Geode
> model, attributes and methods are resolved at runtime during query execution
> - the server does not know what's actually stored in a region until the query
> is executed.
> The disclaimer could be added in one of two places:
> Query Language Restrictions and Unsupported Features
> ([https://geode.apache.org/docs/guide/111/developing/querying_basics/restrictions_and_unsupported_features.html])
> or
> Querying FAQ and Examples
> ([https://geode.apache.org/docs/guide/111/getting_started/querying_quick_reference.html])
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
