Commits

Jean-Tiare Le Bigot  committed 8cd259a

(minor) gramatical/syntaxical fix in changelog

  • Participants
  • Parent commits e09a273

Comments (0)

Files changed (1)

 Removal
 -------
 
-- ``expected_values`` feature was incompatible with the migration engine.
-- ``allow_overwrite`` feature was not needed with ``raise_on_conflict``.
+- ``expected_values`` feature was incompatible with the migration engine
+- ``allow_overwrite`` feature was not needed with ``raise_on_conflict``
 - ``to_db_dict`` and ``from_dict`` are no longer public
 - ``ThroughputError``. Throughput checks are delegated to Amazon's API (thanks kimscheibel)
 
     ``allow_overwrite=False``, replace it with a call to save with
     ``raise_on_conflict=True``. It should handle most if not all use cases. In
     some place, you'll even be able to get rid of ``to_db_dict``. Rename also
-    all instances of ``ExpectedValueError`` to ``ConflictError``.
+    all instances of ``ExpectedValueError`` to ``ConflictError``
 
     ``raise_on_conflict=True`` --> ``allow_overwrite=False`` for new objects
     ``raise_on_conflict=True`` --> ``expected_values=...`` for existing objects
 
 data (de-)serialization
     ``from_dict`` and ``to_db_dict`` have been moved to private ``_from_db_dict``
-    and ``_to_db_dict``. Any direct use of these should be avoided.
-    ``_from_db_dict`` *will* mark data as coming from the DB.
+    and ``_to_db_dict``. Any direct use of these should be avoided
+    ``_from_db_dict`` *will* mark data as coming from the DB
 
     - ``from_dict`` for initialization should be replaced by ``__init__(**kwargs)``
     - ``to_db_dict`` for data export should be replaced by ``to_json_dict``
 Changes
 -------
 
-- fix bug #11 in delete. Keys where not serialized.
+- fix bug #11 in delete. Keys were not serialized
 
 
 ====================
 Known bugs - limitations
 ------------------------
 
-- #7 Can't save models where a datetime field is nested in a dict/list.
-- Can't use ``datetime`` objects in ``scan`` and ``query`` filters.
+- #7 Can't save models where a datetime field is nested in a dict/list
+- Can't use ``datetime`` objects in ``scan`` and ``query`` filters
 - DynamoDBModel.from_dict() does not check types as opposed to ``__init__()``
 
 ====================
 
 autoinc
     For all tables relying on autoinc feature, manually move element
-    at ``'hash_key' = 0`` to ``'hash_key' = -1``.
+    at ``'hash_key' = 0`` to ``'hash_key' = -1``
 
 transactions
     Should be retro-compatible but you are strongly advised to adopt the
-    new API.
+    new API
     - specify ``targets`` and ``setters`` via ``Transactions._get_transactors``
     - avoid any use of ``Transactions._get_target`` and ``Transactions._alter_target``
     - save is now called automatically as long as at least 1 write was attempted