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

Database Migration Meta Issue #165

Open
2 tasks
PGijsbers opened this issue Jul 12, 2024 · 2 comments
Open
2 tasks

Database Migration Meta Issue #165

PGijsbers opened this issue Jul 12, 2024 · 2 comments
Labels
database Something to address on a database level

Comments

@PGijsbers
Copy link
Contributor

This is a collection of proposed database changes:

@PGijsbers PGijsbers added the database Something to address on a database level label Jul 12, 2024
@PGijsbers
Copy link
Contributor Author

The flow (implementation) server logic treats (name, external_version) as a unique tuple, but this is not enforced at the database level.

@PGijsbers
Copy link
Contributor Author

The flow (implementation) table has an uploadDate that does not have a default. I imagine that other tables also have this. I do not know why this is not default at the database level.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
database Something to address on a database level
Projects
None yet
Development

No branches or pull requests

1 participant