If the syntax effectively does nothing I do not see the point of adding it.
CQL is never going to be 100% compatible ANSI-SQL dialect.
On Sat, Mar 2, 2013 at 12:19 PM, Michael Kjellman
<mkjell...@barracuda.com>wrote:
> Might want to create a Jira ticket at issues.apache.org instead of
> submitting the bug report thru email.
>
> On Mar 2, 2013, at 3:11 AM, "Andrew Prendergast" <a...@andrewprendergast.com>
> wrote:
>
> > *DESCRIPTION*
> >
> > When creating a table in all ANSI-SQL compliant RDBMS' the VARCHAR
> datatype
> > takes a numeric parameter, however this parameter is generating errors in
> > CQL3.
> >
> > *STEPS TO REPRODUCE*
> >
> > CREATE TABLE test (id BIGINT PRIMARY KEY, col1 VARCHAR(256)); // emits
> Bad
> > Request: line 1:54 mismatched input '(' expecting ')'
> >
> > CREATE TABLE test (id BIGINT PRIMARY KEY, col1 VARCHAR); // this works
> >
> > *SUGGESTED RESOLUTION*
> >
> > The current fail-fast approach does not create the column so that the
> user
> > is 100% clear that the length parameter means nothing to NOSQL.
> >
> > I would like to propose that the column length be allowed in the grammar
> > (but ignored by cassandra), allowing better ANSI-SQL client
> compatibility.
>
> Copy, by Barracuda, helps you store, protect, and share all your amazing
>
> things. Start today: www.copy.com.
>
