All Versions
125
Latest Version
Avg Release Cycle
-
Latest Release
-

Changelog History
Page 7

  • v0.15.2 Changes

    • The auto_now_add argument of DatetimeField is handled correctly in the SQLite backend.
    • unique_together now creates named constrains, to prevent the DB from auto-assigning a potentially non-unique constraint name.
    • Filtering by an auto_now field doesn't replace the filter value with now() anymore.
  • v0.15.1 Changes

    • ๐Ÿ– Handle OR'ing a blank Q() correctly (#240)
  • v0.15

  • v0.14.2 Changes

    • A Field name of alias is now no longer reserved.
    • โช Restored support for inheriting from Abstract classes. Order is now also deterministic, with the inherited classes' fields being placed before the current.
  • v0.14.1 Changes

    • ManyToManyField is now a function that has the type of the relation for autocomplete, this allows for better type hinting at less effort.
    • โž• Added section on adding better autocomplete for relations in editors.
  • v0.14

  • v0.13.12 Changes

    • Reverted "The Field class now calls super().__init__, so mixins are properly initialised." as it was causing issues on Python 3.6.
  • v0.13.11 Changes

    • ๐Ÿ›  Fixed the _FieldMeta class not to checking if the 1st base class was Field, so would break with mixins.
    • The Field class now calls super().__init__, so mixins are properly initialised.
  • v0.13.10 Changes

    • Names ForeignKey constraints in a consistent way
  • v0.13.9 Changes

    • Fields can have 2nd base class which makes IDEs know python type (str, int, datetime...) of the field.
    • The type parameter of Field.__init__ is removed, instead we use the 2nd base class
    • Foreign keys and indexes are now defined correctly in MySQL so that they take effect as expected
    • MySQL now doesn't warn of unsafe index creation anymore