[
https://issues.apache.org/jira/browse/CALCITE-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16549397#comment-16549397
]
Enrico Olivelli commented on CALCITE-2395:
------------------------------------------
Except from SQL92 standard I cannot find any different cases of SELECT xxx FOR
UPDATE OF id,id,id....
in PostGre seems that they support 'FOR UPDATE' with 'OF' and docs tell about
'*tables*'
see:
https://www.postgresql.org/docs/9.5/static/sql-select.html
In Oracle I am finding only examples like this
[https://www.techonthenet.com/oracle/cursors/for_update.php]
that is
{code:java}
CURSOR xxx IS
SELECT xxx
FROM ...
FOR UPDATE OF table.colum, table.column2
{code}
So it is only with 'CURSOR' and with a list of *columns* (not tables)
Therefore I can't find any support for "CURSOR IS" in Calcite.
I wonder if and how we can support "FOR UPDATE OF" in a consistent way with DMBS
Maybe I am missing one piece of the story, I am not an Oracle expert.
I am continuing the implementation following [~julianhyde] 's suggestions, but
I would like to have a 'real world' counterpart of what I an doing.
Any help/guidance is really appreciated
> 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)
