Changelog

0.4.1

  • Warning: Stored datetime objects will now be timezone-aware (commit a7c253d)
  • Warning: Stored datetime objects will now keep their microseconds (commit fffe92c)

0.4.0

  • Breakage: Dropping support for python 3.2 due to lack of botocore support
  • Breakage: Changing the list, dict, and bool data types to use native DynamoDB types instead of JSON serializing
  • Breakage and bug fix: Fixing serialization of datetime and date objects (for more info see the commit) (commit df049af)
  • Feature: Can now do ‘contains’ filters on lists
  • Feature: Fields support multiple validation checks
  • Feature: Fields have an easy way to enforce non-null values (nullable=False)

Data type changes are due to an update in the DynamoDB API

0.3.0

  • Breakage: Engine namespace is slightly different. If you pass in a string it will be used as the table name prefix with no additional ‘-‘ added.

0.2.1

  • Breakage: Certain queries may now require you to specify an index where it was auto-detected before
  • Feature: Queries can now filter on non-indexed fields
  • Feature: More powerful “sync-if” constraints
  • Feature: Can OR together filter constraints in queries

All changes are due to an update in the DynamoDB API

0.2.0

  • Breakage: Engine no longer accepts boto connections (using dynamo3 instead)
  • Breakage: Removing S3Type (no longer have boto as dependency)
  • Feature: Support Python 3.2 and 3.3
  • Feature: .count() terminator for queries (commit bf3261c)
  • Feature: Can override throughputs in Engine.create_schema() (commit 4d1abe0)
  • Bug fix: Engine namespace is truly isolated (commit 3b4fad7)

0.1.3

0.1.2

0.1.1

0.1.0

  • First public release