Issues
- timezone is ignored in select timestampPYTHON-414Resolved issue: PYTHON-414
- Compact tables with no clustering columns incorrectly considered cql-incompatiblePYTHON-360Resolved issue: PYTHON-360Adam Holmberg
- driver crash on pypy-2.5PYTHON-247Resolved issue: PYTHON-247Kishan Karunaratne
- High CPU utilization when using asyncore event loopPYTHON-239Resolved issue: PYTHON-239
- Ability to pass MetricRegistry for ClusterPYTHON-233Resolved issue: PYTHON-233
- list.remove(x): x not in listPYTHON-232Resolved issue: PYTHON-232
- OrderedMap does not compare Unicode to ASCII strings properlyPYTHON-231Resolved issue: PYTHON-231Adam Holmberg
- simple script results in "Exception in thread Connection heartbeat (most likely raised during interpreter shutdown)"PYTHON-229Resolved issue: PYTHON-229Adam Holmberg
- Evict UDTs from UserType cache on changePYTHON-226Resolved issue: PYTHON-226
- Frequent "Host X has been marked down"PYTHON-225Resolved issue: PYTHON-225
- Tuple param improperly encoded as arrayPYTHON-221Resolved issue: PYTHON-221
- Validate min/max request thresholds for connection pool scalingPYTHON-220Resolved issue: PYTHON-220
- Show warning when the wrong config is passed to SimpleStatementPYTHON-219Resolved issue: PYTHON-219
13 of 13
timezone is ignored in select timestamp
Duplicate
Description
Environment
None
Pull Requests
None
Created September 26, 2015 at 5:34 PM
Updated September 29, 2015 at 2:44 PM
Resolved September 29, 2015 at 2:44 PM
Activity
Show:
Adam HolmbergSeptember 29, 2015 at 2:44 PM
This is by design. It is common for the database layer and client driver to work in UTC and be timezone agnostic. When to add timezone information is application-specific, and sometimes requires external dependencies. With cqlsh integration it makes sense to localize for human readability.
We have this discussion open in PYTHON-145, where we may introduce a way to inject default timezone information
Also a ticket to document the tradeoff in https://datastax-oss.atlassian.net/browse/PYTHON-394#icft=PYTHON-394
I am using following statement to insert a row with timestamp:
insert into user_feed_123 (userid, seqno , generation_time ) VALUES ( 'A', 1234, 1443171171000)And cqlsh shows me output as:
userid | seqno | generation_time
--------+--------+--------------------------
A | 1234 | 2015-09-25 14:22:51+0530
GMT + 0530 is my local timezone.
But when I try to get the row using python, I am getting:
Row(userid='A', seqno=1234, generation_time=datetime.datetime(2015, 9, 25, 8, 52, 51))
It is ignoring timezone. Should give it at least in local timezone.