You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/09/11 05:50:21 UTC
[jira] [Created] (PHOENIX-3263) Allow comma before CONSTRAINT to be
optional
James Taylor created PHOENIX-3263:
-------------------------------------
Summary: 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)