[
https://issues.apache.org/jira/browse/CASSANDRA-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14136070#comment-14136070
]
Benedict commented on CASSANDRA-7523:
-------------------------------------
bq. Do we need to support "empty" values on new types? seems to me we could
explicitly forbid them, or would thrift clients still expect to be able to set
this to empty? What's to stop is introducing semantics for new types that
prevent this, so we can start stamping it out?
bq. Good question. I went with an implementation that was consistent with the
rest of the code-base but can see the argument either way.
[~slebresne] [~iamaleksey] any thoughts on this?
> 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)
