Skip to content

Releases: reddit/cqlmapper

v0.3.0

08 Feb 19:45
Compare
Choose a tag to compare

The only change in this release is to rename the published package to reddit-cqlmapper so it can be published to PyPI.

v0.2.4

27 Mar 23:52
0cb56af
Compare
Choose a tag to compare

This release is the same as v0.2.3, just with the version tag incremented properly in setup.py.

v0.2.3

27 Mar 23:50
Compare
Choose a tag to compare

This release fixes a bug in load_many where the query generated would use the incorrect column name if the Column made use of the db_field attribute.

v0.2.2

03 Jan 20:33
Compare
Choose a tag to compare
  • Update the integration tests to retry the Cassandra connection a couple of times before failing
  • Splat out column names rather than using 'SELECT *' in 'load_many'

v0.2.1

10 Oct 00:13
50e05ab
Compare
Choose a tag to compare

Add load_many to model.BaseModel as an easy way to load multiple models concurrently.

v0.2.0

08 Aug 22:36
74e63b7
Compare
Choose a tag to compare
Remove "beta" tag from version

v0.2.0-beta.1

07 Aug 23:21
Compare
Choose a tag to compare
v0.2.0-beta.1 Pre-release
Pre-release

Update the version in "setup.py".

v0.2.0-beta

06 Aug 22:07
Compare
Choose a tag to compare
v0.2.0-beta Pre-release
Pre-release

Beta release for v0.2.0. This change is meant to coincide with the release of Baseplate 1.0. In terms of "Lines of Code", most of the updates are just running "black" and "reorder-python-imports". We also moved the dev environment from Vagrant + puppet to using docker-compose.

This release has a breaking change it how we configure the underlying Session object used by the cqlmapper Connection. Rather than setting session.row_factory manually, we use a custom ExecutionProfile for cqlmapper. This means that it won't work for cases where we were manually setting this like session.default_consistency_level and those changes will need to be done in ExecutionProfile-s instead. This is the preferred way of doing this come Baseplate 1.0 so it should be done along side that.

There is also another breaking change that goes along with this. Since we are using a custom ExecutionProfile, connection.session.execute will no longer return a dict unless you have configured it to by default, so services that are calling that directly (say to make concurrent requests) will need to account for that. You can do that by either using execution_profile=EXC_PROFILE_CQLMAPPER when making the call, configuring your default profile to use row_factory=dict_factory, or updating your code to expect namedtuples rather than dicts in those cases.

backport fixes from cqlengine

22 Apr 22:07
Compare
Choose a tag to compare
v0.1.1

Cut version 0.1.1

v0.1.0

08 May 18:05
v0.1.0
Compare
Choose a tag to compare
  • initial release