What's Changed

• Fixes citus 11.3 identity column bigint constraint by @gurkanindibay in https://github.com/citusdata/django-multitenant/pull/181
• Adds Blogpost into Readme and updates python packages by @gurkanindibay in https://github.com/citusdata/django-multitenant/pull/180
• Fix mispelling in README.md by @jnovinger in https://github.com/citusdata/django-multitenant/pull/182
• Updating docs to show the importance of unsetting the tenant in a middleware by @arpanpreneur in https://github.com/citusdata/django-multitenant/pull/173
• Updates docs requirement version by @gurkanindibay in https://github.com/citusdata/django-multitenant/pull/183
• Adds new python versions for dj3.2 by @gurkanindibay in https://github.com/citusdata/django-multitenant/pull/188
• Update README.md by @ieaves in https://github.com/citusdata/django-multitenant/pull/189
• Updates package versions by @gurkanindibay in https://github.com/citusdata/django-multitenant/pull/191
• Adds additional citus and django versions by @gurkanindibay in https://github.com/citusdata/django-multitenant/pull/197

New Contributors

• @jnovinger made their first contribution in https://github.com/citusdata/django-multitenant/pull/182
• @arpanpreneur made their first contribution in https://github.com/citusdata/django-multitenant/pull/173
• @ieaves made their first contribution in https://github.com/citusdata/django-multitenant/pull/189

Full Changelog: https://github.com/citusdata/django-multitenant/compare/v3.2.1...v4.0.0

• Add m2m with no through_defaults fix (#170)

• Adds DjangoRestFramework support (#157)

• Adds guidelines to get model in migration (#167)

Fixes #164 ManyToMany Non tenant model save issue

• Adds support for Django 4.1

• Adds support for setting tenant automatically for ManyToMany related model

• Fixes invalid error message problem in case of invalid field name

• Adds support for getting models using apps.get_model

• Removes reserved tenant_id limitation by introducing TenantMeta usage

• Introduces ReadTheDocs documentation

This release adds Django 4.0 support.

It also drops support for the following EOLed Django and Python versions:

1. Python 2.7
2. Django 1.11
3. Django 3.1

Features

• Backwards migration for Distribute migration using undistribute_table()
• Add tests for Django 3.2 and Python 3.9

Fixes

• Fix migrations on Django 3.0+
• Fix aggregations using annotate

Fix the process of running old migrations when the model has been deleted from the code.

Add tests to confirm the join condition in subqueries includes tenant column.

Add tests for django 2.2

In version 2.0.6, a bug was introduced when doing

set_current_tenant(my_tenant)
MyModel.objects.create(name='test')

the tenant column wasn't filled. This fixes the issue

Fix recursive loop in warning for fields when joining without current_tenant set

• Users can now have their own queryset_class in TenantManager

Here is an example of the usecase

class TaskQueryset(models.QuerySet):
    def opened(self):
        return self.filter(opened=True)

    def closed(self):
        return self.filter(opened=False)

class TaskManager(TenantManagerMixin, models.Manager):
    _queryset_class = TaskQueryset

    def opened(self):
        return self.get_queryset().opened()

    def closed(self):
        return self.get_queryset().closed()


class Task(TenantModelMixin, models.Model):
    name = models.CharField(max_length=255)
    project = TenantForeignKey(Project, on_delete=models.CASCADE,
                               related_name='tasks')
    account = models.ForeignKey(Account, on_delete=models.CASCADE)
    opened = models.BooleanField(default=True)

    objects = TaskManager()

    tenant_id = 'account_id'

• Clean the delete code to ensure deleting rows only related to current tenant

In this version is introduced the concept of having multiple tenants as the current one making it possible to do

set_current_tenant([tenant_1, tenant_2])

It will add to the filter tenant_id__in=current_tenant instead of tenant_id=current_tenant

1. Add TenantForeignKey to emulate composite foreign keys between tenant related models.
2. Split apart library into multiple files. Importing the utility function get_current_tenant would cause errors due to the import statement triggering evaluation of the TenantModel class. This would cause problems if TenantModel were evaluated before the database backend was initialized.
3. Added a simple TenantOneToOneField which does not try to enforce a uniqueness constraint on the ID column, but preserves all the relationship semantics of using a traditional OneToOneField in Django.
4. Overrode Django's DatabaseSchemaEditor to produce foreign key constraints on composite foreign keys consisting of both the ID and tenant ID columns for any foreign key between TenantModels
5. Monkey-patched Django's DeleteQuery implementation to include tenant_id in its SQL queries.

Some bug fixes.