[
https://issues.apache.org/jira/browse/CASSANDRA-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450709#comment-13450709
]
Michael Krumpholz commented on CASSANDRA-4628:
----------------------------------------------
{quote}
that is an issue with the jdbc driver then, not Cassandra
{quote}
That would be the case only if that class (JdbcDate) would NOT be part of
cassandra (apache-cassandra-clientutil-x.x.x.jar) but located in the jdbc
lib/jar in the project at google.
{quote}
Oops, I guess that is our code.
{quote}
Right! For now it's within cassandra code and included as dependency in
cassandra-jdbc. If this type class and the meaning of if should change with
CASSANDRA-4495 then the code should be moved to the jdbc project or a update
there should be done. I don't know how much the casandra dev team is involved
with the cassandra-jdbc project...
> CQL/JDBC: date vs. timestamp issues
> -----------------------------------
>
> Key: CASSANDRA-4628
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4628
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Michael Krumpholz
> Priority: Minor
> Labels: cql, jdbc
> Fix For: 1.2.0 beta 1
>
>
> Cassandra's datatypes only have one Date/Time type named timestamp containing
> both date and time. Calling the validator
> org.apache.cassandra.db.marshal.DateType might be OK in general but can be
> confusing in the jdbc context where there is a distinction between date, time
> and timestamp. In terms of jdbc there should be more datatypes for dates and
> times or the jdbc driver should take one of the following options:
> - stick to timestamp
> - check if the date has a time part and distinguish by the data between date
> and timestamp automatically
> - use distinct datatypes according to the jdbc spec, the types would need to
> be in cassandra then too
> Now back to my actual problem:
> org.apache.cassandra.cql.jdbc.JdbcDate returns Types.DATE in getType(). Even
> if having inserted a complete date with time (making it a timestamp) the
> ResultSetMetaData.getColumnType() implementation still returns Types.DATE
> (source of this is in JdbcDate). If some other java code (where i don't have
> access to) uses the metadata to get the type and then getDate() to get the
> value the time is cut off the value and only the date is returned.
> But the ResultSet.getObject() implementation returns a complete
> java.util.Date including the time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
