[
https://issues.apache.org/jira/browse/CASSANDRA-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-2445:
--------------------------------------
Description:
We should support SQL data types where possible:
(sql -> cassandra)
varint -> int
bigint -> long
varchar, text -> utf8
ascii -> ascii (not strictly correct -- sql defines collations for this -- but
close enough for a 1.0)
uuid -> uuid (see CASSANDRA-2233)
bytea -> bytes
IMO the right thing to do is _only_ support the SQL types in CQL CREATE
statements, because there is ambiguity otherwise (in particular with "int").
was:
We should support SQL data types where possible:
(sql -> cassandra)
varint -> int
bigint -> long
varchar, text -> utf8
ascii -> ascii (not strictly correct -- sql defines collations for this -- but
close enough for a 1.0)
uuid -> uuid (see CASSANDRA-2233)
bytea -> bytes
IMO the right thing to do is _only_ support the SQL types from CQL, because
there is ambiguity otherwise (in particular with "int").
I believe the only changes needed is to the comparatorType definition in Cql.g
and to the corresponding Map in CreateColumnFamilyStatement.
> Support SQL data types in CQL
> -----------------------------
>
> Key: CASSANDRA-2445
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2445
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Fix For: 0.8
>
> Attachments: 2445.txt
>
>
> We should support SQL data types where possible:
> (sql -> cassandra)
> varint -> int
> bigint -> long
> varchar, text -> utf8
> ascii -> ascii (not strictly correct -- sql defines collations for this --
> but close enough for a 1.0)
> uuid -> uuid (see CASSANDRA-2233)
> bytea -> bytes
> IMO the right thing to do is _only_ support the SQL types in CQL CREATE
> statements, because there is ambiguity otherwise (in particular with "int").
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
