[
https://issues.apache.org/jira/browse/CASSANDRA-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352667#comment-14352667
]
Sylvain Lebresne commented on CASSANDRA-7523:
---------------------------------------------
bq. Should we instead consider v3's spec frozen and have the formal type ID's
for these types be added in as a subtask on CASSANDRA-8043?
That one. Adding new codes to v3 would confuse drivers (at least we can't
assume it won't). It's ok though, the new types will just be sent as "custom"
types on v3 but drivers that wish so can still support them that way.
> 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
> Labels: client-impacting, docs
> Fix For: 2.1.4
>
>
> 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)
