[CASSANDRA-4628] CQL/JDBC: date vs. timestamp issues

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 1.2.0 beta 1
• Labels: cql jdbc
• Severity: Low
• Assignee: Michael Krumpholz
• Reporter: Michael Krumpholz

Authors

Michael Krumpholz

Reviewers

Jonathan Ellis

• Created: 07/Sep/12 07:25
• Updated: 16/Apr/19 09:32
• Resolved: 07/Sep/12 15:23

Description

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.