[ https://issues.apache.org/jira/browse/PHOENIX-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15488424#comment-15488424 ]
Maryann Xue commented on PHOENIX-3263: -------------------------------------- Thanks for you response, [~lomoree]! But you won't be able to commit it :) You can either create a fork of the Apache Phoenix project on github and work on the "calcite" branch of your fork, or submit a patch to this JIRA issue. Then after it passes the review, I can commit it for you. > Allow comma before CONSTRAINT to be optional > -------------------------------------------- > > Key: PHOENIX-3263 > URL: https://issues.apache.org/jira/browse/PHOENIX-3263 > Project: Phoenix > Issue Type: Sub-task > Reporter: James Taylor > > In Phoenix, the comma before the CONSTRAINT is optional (which matches > Oracle). Can this be supported in Calcite Phoenix? > For example, this is ok in Phoenix: > {code} > CREATE TABLE T ( > K VARCHAR > CONSTRAINT PK PRIMARY KEY (K)); > {code} > as is this: > {code} > CREATE TABLE T ( > K VARCHAR, > CONSTRAINT PK PRIMARY KEY (K)); > {code} > If this is not feasible, we could require the comma and change the tests. > This is leading to a lot of failures. -- This message was sent by Atlassian JIRA (v6.3.4#6332)