Changelogs » Django-idmap

PyUp Safety actively tracks 263,016 Python packages for vulnerabilities and notifies you when to upgrade.

Django-idmap

1.0.3

...................
  
  Added:
  - Django 2.0 support
  
  Removed:
  - Django 1.9 and 1.10 support (may still work)

1.0.2

...................
  
  Fixed:
  - issue 3: IdMapQuerySet.values_list() and .values() now work correctly

1.0.1

...................
  
  Fixed:
  - refresh_from_db inconsistency when using weak references

1.0

-----------------
  
  Added:
  - Support of multiple databases for one model
  - Renames ``flush_cache`` function to ``flush``
  - ``pre_flush`` and ``post_flush`` signals
  - Support for Django 1.11 and Python 3.6
  - Support of proxy models using proxy groups
  - Support of options in django's Meta

0.4

-----------------
  
  Added:
  - Django 1.9 support
  
  Removed:
  - Django < 1.8 support (may still work with 1.7)

0.3.3

...................
  
  Added:
  - Django 1.8 compatibility

0.3.2

...................
  
  Fixed:
  - Where clause issue on Django 1.4, 1.5 and 1.7
  
  Added:
  - already loaded instance are searched even after hitting the database, e.g.
  when making a query on non-pk parameters, for the sake of id consistency

0.3.1

...................
  
  Fixed:
  - use_strong_refs option bug

0.3

-----------------
  
  Added:
  - use_strong_refs option
  - Django 1.4 to 1.7 compatibility
  - Python 3 compatibility

0.2.1

...................
  
  Added:
  - multi-threading ability (thanks to Andreas Pelme)
  
  Fixed:
  - bugs introduced prior to fork

0.2

-----------------
  
  - Forked django-idmapper