[ https://issues.apache.org/jira/browse/CALCITE-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16532131#comment-16532131 ]
Julian Hyde commented on CALCITE-2395: -------------------------------------- I think we'd do this as part of the core parser if this is standard SQL. (Can you please read the standard and find out for sure?) There is a strong case because (to my knowledge) at least Oracle and PostgreSQL support it. I'd favor not just "SELECT ... FOR UPDATE" but "SELECT ... FOR UPDATE OF table [, table]...". If we don't do it as core we could do it as an extension. > 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)