[
https://issues.apache.org/jira/browse/CALCITE-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16549630#comment-16549630
]
Julian Hyde commented on CALCITE-2395:
--------------------------------------
IBM DB2 also has an [update
clause|https://www.ibm.com/support/knowledgecenter/en/SSEPEK_10.0.0/sqlref/src/tpc/db2z_sql_updateclause.html].
I see that in SQL:2014 {{<updatability clause>}} is only part of a {{<cursor
specification>}}. I wouldn't worry too much about that. We may implement
cursors at some point, or we may not. The main thing is that we only allow the
clause on a top-level query (i.e. not on sub-queries or views).
> 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)
