Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Integrate basic sharding #40

Open
lorinkoz opened this issue Jun 25, 2020 · 0 comments
Open

Integrate basic sharding #40

lorinkoz opened this issue Jun 25, 2020 · 0 comments
Assignees
@lorinkoz
Milestone
v1.5

Comments

@lorinkoz
Copy link
Owner

lorinkoz commented Jun 25, 2020 •
edited

Is it possible to control schemas in more than one database with a smart routing?

Current challenges:

  • Active schema can no longer be tracked in the connection object.
  • Management commands now require a database parameter that may conflict in some cases with the existing commands.
  • Duplication of content types across databases, requires to review the caching behavior (although it seems multi-database friendly)
  • Requires API decision on how to map dynamic tenants with their database (could be a database field or a model method)
  • Requires API decision on how to specify the databases that can be used for dynamic tenants (public and CLONE_REFERENCE must always be on every database)
@lorinkoz lorinkoz added the enhancement New feature or request label Jun 25, 2020
@lorinkoz lorinkoz self-assigned this Jun 25, 2020
@lorinkoz lorinkoz added this to the v1.0 milestone Jun 25, 2020
This was referenced Jun 25, 2020
Merged
Closed
@lorinkoz lorinkoz changed the title Integrated basic sharding Integrate basic sharding Sep 3, 2020
@lorinkoz lorinkoz modified the milestones: v1.0, v1.5 Dec 13, 2020
@lorinkoz lorinkoz removed the enhancement New feature or request label Jul 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lorinkoz lorinkoz

Labels
None yet
Projects
None yet
Milestone
v1.5
Development

Successfully merging a pull request may close this issue.

Experiment with distributing schemas across multiple databases lorinkoz/django-pgschemas
1 participant
@lorinkoz