[
https://issues.apache.org/jira/browse/CALCITE-5612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17777362#comment-17777362
]
Julian Hyde commented on CALCITE-5612:
--------------------------------------
This case illustrates something I've been saying for a long time: Don't ask me
to review things. If my name is against a case/PR others will be less inclined
to review it.
I often comment when a jira case is first logged. I'm trying to make sure that
the project is headed in the right direction. After I've made those comments, I
have very little time to review iterations of the PR.
> Babel parser should support PostgreSQL's SET TRANSACTION command
> ----------------------------------------------------------------
>
> Key: CALCITE-5612
> URL: https://issues.apache.org/jira/browse/CALCITE-5612
> Project: Calcite
> Issue Type: Bug
> Components: babel
> Affects Versions: 1.34.0
> Reporter: Dmitry Sysolyatin
> Assignee: Dmitry Sysolyatin
> Priority: Major
> Labels: pull-request-available
>
> SET TRANSACTION — set the characteristics of the current transaction
> Specification [1]:
> {code}
> SET TRANSACTION transaction_mode [, ...]
> SET TRANSACTION SNAPSHOT snapshot_id
> SET SESSION CHARACTERISTICS AS TRANSACTION transaction_mode [, ...]
> where transaction_mode is one of:
> ISOLATION LEVEL { SERIALIZABLE | REPEATABLE READ | READ COMMITTED | READ
> UNCOMMITTED }
> READ WRITE | READ ONLY
> [ NOT ] DEFERRABLE
> {code}
> [1] https://www.postgresql.org/docs/current/sql-set-transaction.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
