cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Shaw (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2530) Additional AbstractType data type definitions to enrich CQL
Date Sat, 04 Jun 2011 14:51:47 GMT


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:
>             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:

View raw message