++++++++++++++++
Incompatible changes:
* Dropped support for Python < 3.6.
* Dropped support for Django < 2.2.
* Dropped support for SQLALchemy < 1.4.
* Removed ``aldjemy.to_list``.
* Removed ``aldjemy.core.get_meta``.
* Removed ``aldjemy.core.Cache.models``.
* Removed ``aldjemy.core.Cache.sa_models``.
* Removed ``aldjemy.core.Cache.meta``.
* Removed ``aldjemy.orm.prepare_models``.
* Removed ``aldjemy.table.get_all_django_models``.
* Merged ``aldjemy.types`` and ``aldjemy.postgres`` into ``aldjemy.table``.
Features:
* Django's `JSONField` is now handled by default as a postgres `JSONB` type.
Deprecations:
* Deprecated ``aldjemy.core.Cache`` without a warning or replacement.
To get the ``MetaData`` instance that Aldjemy used
from a model like ``auth.User``,
call ``auth.User.sa.model.metadata``.
If you're wanting to get the Aldjemy model for a through table,
like the through table for ``auth.User.groups``,
get the Django model for that through table,
and then access the ``sa`` attribute as normal by calling
``auth.User._meta.get_field('groups').remote_field.through.sa``.
Fixes:
* Silence some warnings from SQLAlchemy 1.4.
Many to many fields create duplicated active relationships,
which SQLAlchemy discourages.
However, this retains backward compatibility
and seems like a reasonable compromise for translating Django models.