[
https://issues.apache.org/jira/browse/CASSANDRA-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044304#comment-13044304
]
Rick Shaw commented on CASSANDRA-2530:
--------------------------------------
I see your point. What is being lost is the fact that the writer intends the
date to be interpreted in EST for all subsequent readers. But that is not
recorded by any binary data type: j.u.Date,j.s.Date,j.s.Time, j.s.Timestamp,
or even j.u.UUID. Really it is only String/text that can convey that intent of
the original writer.
The SQL Timestamp does not really help in that area. It offers the addition of
more (nanos) accuracy but not "timestamp with timezone" features unless I read
it terribly wrong??
> Additional AbstractType data type definitions to enrich CQL
> -----------------------------------------------------------
>
> Key: CASSANDRA-2530
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2530
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.8.0 beta 2
> Reporter: Rick Shaw
> Priority: Trivial
> Labels: cql
> Attachments: patch-to-add-4-new-AbstractTypes-and-CQL-support-v4.txt,
> patch-to-add-4-new-AbstractTypes-and-CQL-support-v5.txt
>
>
> Provide 5 additional Datatypes: ByteType, DateType, BooleanType, FloatType,
> DoubleType.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
