-
Notifications
You must be signed in to change notification settings - Fork 417
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
feat(score_configs): add table via migration #2126
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ce4f9bb
to
a7e77c5
Compare
785f9ed
to
84987fa
Compare
...es/shared/prisma/migrations/20240522141714_annotation_config_add_fk_project_id/migration.sql
Outdated
Show resolved
Hide resolved
packages/shared/prisma/migrations/20240522141943_scores_add_annotation_config_id/migration.sql
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
overall looks good to me! added quick note re backfill, i think defaulting here is probably fine and makes this faster to deploy. we can later switch to non-null without default and make sure to always set the type on the application layer
packages/shared/prisma/migrations/20240523115814_scores_backfill_data_type/migration.sql
Outdated
Show resolved
Hide resolved
* make data_type column optional on scores
No description provided.