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.

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

move database.third_parties models into separate apps #646

Open
jacksund opened this issue Apr 19, 2024 · 0 comments
Open

move database.third_parties models into separate apps #646

jacksund opened this issue Apr 19, 2024 · 0 comments
Labels
enhancement New feature or request refactor cleans up code without affecting functionality

Comments

@jacksund
Copy link
Owner

this is only a proposed move right now and it would require a full database reset.

But as datasets are growing (mostly on the molecular side), I'm starting to see that it makes more sense to organize these into apps. For example, the Materials Project database model would be moved into apps.materials_project.models and its name in the database would become materials_project_structures (plus other tables like materials_project_bandstuctures) instead of data_explorer_materialsproject

@jacksund jacksund added enhancement New feature or request refactor cleans up code without affecting functionality labels Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request refactor cleans up code without affecting functionality
Projects
None yet
Development

No branches or pull requests

1 participant