Django-pgschemas

Latest version: v1.0.2

Safety actively analyzes 688433 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 5

0.11.0

- [INTERNAL] Now storing active schema in `asgiref.local` instead of the Django database connection

0.10.0

- Added support for Django 4.1

0.9.0

- Added support for Django 4
- Dropped support for Django < 3.1 and Python < 3.8

0.8.0

What's Changed
* Updated dependencies
* Added feature to redirect to the primary domain

**Full Changelog**: https://github.com/lorinkoz/django-pgschemas/compare/v0.7.0...v0.8.0

0.7.0

This is a major refactor of the package.

Breaking changes

- Changed public API for getting/setting active schema. Public API is now `get_current_schema`, `activate(schema)`, `activate_public()`. Any schema descriptor can still be used as context manager.
- Changed location of tenant model and domain model in settings. `TENANT_MODEL` and `DOMAIN_MODEL` keys are now under `TENANTS["default"]` instead of `TENANTS["public"]`. This is required for future static-tenant-only configurations.
- Module `cache` renamed to `contrib.cache`.
- Module `contrib.channels` renamed to `contrib.channels2`.
- Added module `contrib.channels3`.
- Management command option `--executor {sequential, parallel}` renamed to `--parallel`.
- All signals renamed. Added `schema_activate` signal.

0.6.1

- Fixed bug with migrate management command and Django 3.

Page 3 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.