[
https://issues.apache.org/jira/browse/CALCITE-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16549780#comment-16549780
]
Julian Hyde commented on CALCITE-2395:
--------------------------------------
Can we defer that decision, until we know what people need? There won't be any
changes to the parser, only to the validator.
The standard is clear: it is a list of column names, and the column names are
simple identifiers, and each column name is an alias returned by the result
set. (Similar to what you can include in the ORDER BY clause.)
But it doesn't seem too hard to also allow table references and qualified
column references:
{code}select emp.name as emp_name, ...
from emp, dept
for update of emp_name, emp, dept.name{code}
It would get ambiguous if, say, dept were used more than once in the query, but
I don't worry too much about that.
> Support SELECT xxx FROM TABLE FOR UPDATE syntax
> -----------------------------------------------
>
> Key: CALCITE-2395
> URL: https://issues.apache.org/jira/browse/CALCITE-2395
> Project: Calcite
> Issue Type: New Feature
> Components: core
> Affects Versions: 1.16.0
> Reporter: Enrico Olivelli
> Assignee: Julian Hyde
> Priority: Major
>
> I am using Calcite SQL Parser and Volcano Planner.
> I need to support SQL syntax
> SELECT ... FROM table FOR UPDATE
>
> see for instance PostGre docs
> [https://www.postgresql.org/docs/9.5/static/sql-select.html.]
>
> I would like at least to support this syntax at SQL Parser level, the 'for
> update' spec should be reported by the RelNode so that the system can take it
> into account and perform explicit locking.
>
> Linked downstream project issue:
> https://github.com/diennea/herddb/issues/228
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
