add migrations for the updated spans table with project id #152
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Important
This PR updates the
spans
table to includeproject_id
as part of the primary key, modifies related constraints and indexes, and updates thelabeling_queue_data
table and related code to reflect these changes.project_id
column tospans
table, making it part of the primary key.spans
table with new foreign keyspans_project_id_fkey
and indexspans_project_id_idx
.span_id
column tolabeling_queue_data
table.0002_next_tusk.sql
to0002_cold_romulus.sql
and update to includespan_id
inlabeling_queue_data
.0003_cultured_tinkerer.sql
to drop and recreatespans_pkey
withproject_id
.0002_snapshot.json
and0003_snapshot.json
to reflect schema changes._journal.json
with new migration entries.relations.ts
to includeproject
relation inspansRelations
.schema.ts
to define new primary key and foreign key constraints forspans
.This description was created by for bb9b9f9. It will automatically update as commits are pushed.