forked from django-tenants/django-tenants
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update #2
Open
benjy3gg
wants to merge
380
commits into
mecodia:master
Choose a base branch
from
django-tenants:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… to match with sub-folder tenant value. Signed-off-by: Alis Rasic <[email protected]>
`django.test.Client` inheritance have `RequestFactory`, so, defining `TenantRequestFactory(RequestFactory)` on `TenantClient` is causing some annotations issues. This change creates a clean base class so we can use on both `TenantRequestFactory` and `TenantClient`
Bumps [django](https://github.com/django/django) from 4.0.4 to 4.0.6. - [Release notes](https://github.com/django/django/releases) - [Commits](django/django@4.0.4...4.0.6) --- updated-dependencies: - dependency-name: django dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
Bump django from 4.0.4 to 4.0.6
Fix TenantClient annotations
Fix: add --prune option for django 4.1 compatibility
- always use the latest from each release! - remove Postgres 10 b/c it will be EOL in Nov 2022. Django 4.1 already dropped support for it
- remove Python 3.7 - add Django 4.1
This setting defauls to True and will be deprecated in Django 5.0: https://docs.djangoproject.com/en/4.0/ref/settings/#use-l10n
Bumps [django](https://github.com/django/django) from 4.0.6 to 4.0.7. - [Release notes](https://github.com/django/django/releases) - [Commits](django/django@4.0.6...4.0.7) --- updated-dependencies: - dependency-name: django dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
Fixes #802 Notes: - see the issue for background analysis - this patch seems like the easiest fix without refactoring the entire clone_schema() function! Speculation: I think that because IDENTITY columns use sequences internally (opposed to creating sequences explicitly) information_schema doesn't contain information about them anymore (resulting in seq_cnt = 0). However this internal information is still present in pg_catalog which results in an error when trying to grant the permissions. Also possible that at the time the GRANT statement is executed the internal sequences aren't created yet and they are only created only *AFTER* the entire transaction is committed.
Bump django from 5.1 to 5.1.1
…-3.1.4 Bump pyparsing from 3.1.2 to 3.1.4
Bumps [django](https://github.com/django/django) from 5.1.1 to 5.1.2. - [Commits](django/django@5.1.1...5.1.2) --- updated-dependencies: - dependency-name: django dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [sphinx](https://github.com/sphinx-doc/sphinx) from 7.3.7 to 8.1.3. - [Release notes](https://github.com/sphinx-doc/sphinx/releases) - [Changelog](https://github.com/sphinx-doc/sphinx/blob/master/CHANGES.rst) - [Commits](sphinx-doc/sphinx@v7.3.7...v8.1.3) --- updated-dependencies: - dependency-name: sphinx dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
Adds support for deleting domains from existing tenants
Add Support for Managing Domains with Commands
Bump sphinx from 7.3.7 to 8.1.3
Bump django from 5.1.1 to 5.1.2
Bumps [django](https://github.com/django/django) from 5.1.2 to 5.1.3. - [Commits](django/django@5.1.2...5.1.3) --- updated-dependencies: - dependency-name: django dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [codecov/codecov-action](https://github.com/codecov/codecov-action) from 4 to 5. - [Release notes](https://github.com/codecov/codecov-action/releases) - [Changelog](https://github.com/codecov/codecov-action/blob/main/CHANGELOG.md) - [Commits](codecov/codecov-action@v4...v5) --- updated-dependencies: - dependency-name: codecov/codecov-action dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [pyparsing](https://github.com/pyparsing/pyparsing) from 3.1.4 to 3.2.0. - [Release notes](https://github.com/pyparsing/pyparsing/releases) - [Changelog](https://github.com/pyparsing/pyparsing/blob/master/CHANGES) - [Commits](pyparsing/pyparsing@3.1.4...3.2.0) --- updated-dependencies: - dependency-name: pyparsing dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
similar to what was already introduced in d02a4ee. To use it: with schema_context("my_schema", database="replica_db"): pass
WARNING: this commit forces pip to use requirements.txt in CI WARNING: remove Django from requirements.txt b/c version is explicitly configured in CI. For local development we can use whatever version we want (will usually be the latest anyway).
commit 340f137 introduces what appears as a workaround on psycopg3 so that DB cursors cannot be reused. I am not certain but I think this is what causes the number of expected queries, as asserted in the test, to be different between psycopg2 and psycopg3!
Bumps [django](https://github.com/django/django) from 5.1.3 to 5.1.4. - [Commits](django/django@5.1.3...5.1.4) --- updated-dependencies: - dependency-name: django dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
Bump django from 5.1.3 to 5.1.4
Support database alias in schema_context() & tenant_context()
Send a signal before migrations run
Add DEFAULT_NOT_FOUND_TENANT_VIEW setting to allow custom handling of tenant not found scenarios through a configurable view
middleware - Add custom view support for default view tenant not found
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.