Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sun, 10 Apr 2011 05:23:05 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <938997518.47557.1302412985935.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1565311873.47068.1302385265726.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-2445) Support SQL data types in CQL
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018036#comment-13018036 ] 

Hudson commented on CASSANDRA-2445:
-----------------------------------

Integrated in Cassandra #842 (See [https://hudson.apache.org/hudson/job/Cassandra/842/])
    use SQL-ish data types
patch by jbellis and Eric Evans for CASSANDRA-2445


> 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, v1-0001-CASSANDRA-2445-update-documentation.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