[ https://issues.apache.org/jira/browse/CALCITE-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16549816#comment-16549816 ]
Enrico Olivelli commented on CALCITE-2395: ------------------------------------------ I am worrying about the validator: how can I validate the list of identifiers? About the rel2sql and planner: how can I bind each identifier with a table? I will have to generate a TableModify for each identifier and in case of empty list I will have to create one TableModify for each table referred by the query. Thank you for your help, I am still new to Calcite codebase > 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)