openstack/deb-python-cassandra-driver
Code Issues Proposed changes

cqle: Note about Date type in upgrade guide

Browse Source
This commit is contained in:
Adam Holmberg
2015-05-29 15:09:15 -05:00
parent f00bfe746d
commit 38705c229a
2 changed files with 13 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/api/cassandra/cqlengine/columns.rst
View File

@@ -52,7 +52,7 @@ Columns of all types are initialized by passing :class:`.Column` attributes to t
.. autoclass:: Counter
.. autoclass:: Date
.. autoclass:: Date(**kwargs)
.. autoclass:: DateTime(**kwargs)

14
docs/cqlengine/upgrade_guide.rst
View File

@@ -8,13 +8,23 @@ conversion to this package will still require certain minimal updates (namely, i
**THERE IS ONE FUNCTIONAL CHANGE**, described in the first section below.
Functional Change
=================
Functional Changes
==================
List Prepend Reversing
----------------------
Legacy cqlengine included a workaround for a Cassandra bug in which prepended list segments were
reversed (`CASSANDRA-8733 <https://issues.apache.org/jira/browse/CASSANDRA-8733>`_). As of
this integration, this workaround is removed. The first released integrated version emits
a warning when prepend is used. Subsequent versions will have this warning removed.
Date Column Type
----------------
The Date column type in legacy cqlengine used a ``timestamp`` CQL type and truncated the time.
Going forward, the :class:`~.columns.Date` type represents a ``date`` for Cassandra 2.2+
(`PYTHON-245 <https://datastax-oss.atlassian.net/browse/PYTHON-245>`_).
Users of the legacy functionality should convert models to use :class:`~.columns.DateTime` (which
uses ``timestamp`` internally), and use the build-in ``datetime.date`` for input values.
Remove cqlengine
================
To avoid confusion or mistakes using the legacy package in your application, it