Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 16 Sep 2014 19:57:34 +0000 (UTC)
From: "Benedict (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12726245.1404880380000.48158.1410897454665@Atlassian.JIRA>
In-Reply-To: <JIRA.12726245.1404880380000@Atlassian.JIRA>
References: <JIRA.12726245.1404880380000@Atlassian.JIRA>
 <JIRA.12726245.1404880380055@arcas>
Subject: [jira] [Commented] (CASSANDRA-7523) add date and time types
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Benedict commented on CASSANDRA-7523:
-------------------------------------

One last thought to consider: just wondering if it actually makes sense to be using primitive types as the type parameter to AbstractType/TypeSerializer. Why not the joda time types? Generally makes me more comfortable to use stronger types where possible

> add date and time types
> -----------------------
>
>                 Key: CASSANDRA-7523
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7523
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API
>            Reporter: Jonathan Ellis
>            Assignee: Joshua McKenzie
>            Priority: Minor
>             Fix For: 2.1.1, 3.0
>
>
> http://www.postgresql.org/docs/9.1/static/datatype-datetime.html
> (we already have timestamp; interval is out of scope for now, and see CASSANDRA-6350 for discussion on timestamp-with-time-zone.  but date/time should be pretty easy to add.)


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)