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

split databases #85

Open
rmnldwg opened this issue May 18, 2022 · 1 comment
Open

split databases #85

rmnldwg opened this issue May 18, 2022 · 1 comment
Assignees
@rmnldwg
Labels
maintenance e.g. upgrading framework or libraries python Pull requests that update Python code wontfix This will not be worked on

Comments

@rmnldwg
Copy link
Owner

rmnldwg commented May 18, 2022

If the users and patient data were stored in two different databases, I would not need to always recreate all the users when something is broken with the patient data.

Also, this would allow me to delete and recreate the patient database (e.g. on every push to the main branch) from the data in the lyDATA repository programmatically.
@rmnldwg rmnldwg added python Pull requests that update Python code maintenance e.g. upgrading framework or libraries labels May 18, 2022
@rmnldwg rmnldwg self-assigned this May 18, 2022
@rmnldwg rmnldwg added the wontfix This will not be worked on label May 20, 2022
@rmnldwg
Copy link
Owner Author

rmnldwg commented May 20, 2022

From Django's website:

Django doesn’t currently provide any support for foreign key or many-to-many relationships spanning multiple databases.

So, it seems this isn't possible or at least not supported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rmnldwg rmnldwg

Labels
maintenance e.g. upgrading framework or libraries python Pull requests that update Python code wontfix This will not be worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rmnldwg