Skip to content

DM-51936 : Migrate tables for v2 feature development #183

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
Open
wants to merge 1 commit into
base: tickets/DM-51337/release
Choose a base branch
from
Open

DM-51936 : Migrate tables for v2 feature development #183

wants to merge 1 commit into from
+589 −17

Conversation

tcjennings
Copy link
Contributor

feat(db): Add migrations and models for v2 tables

  • these table migrations are subject to change as v2 feature development continues. Expect to denormalize columns from "metadata" fields and potentially apply validation constraints, indexes, and etc.

@tcjennings tcjennings force-pushed the tickets/DM-51396/v2_tables branch from f011891 to b35ea06 Compare June 23, 2025 19:29
@tcjennings tcjennings marked this pull request as ready for review June 23, 2025 19:31
Base automatically changed from tickets/DM-51397/py312_types to tickets/DM-51337/release June 24, 2025 14:28
@tcjennings tcjennings force-pushed the tickets/DM-51396/v2_tables branch from b35ea06 to 9dadfe3 Compare June 24, 2025 14:36
@tcjennings
feat(db): Add migrations and models for v2 tables
ac2ebfb 
feat(db): Extend v2 model fields with pydantic aliases
@tcjennings tcjennings force-pushed the tickets/DM-51396/v2_tables branch from 9dadfe3 to ac2ebfb Compare June 24, 2025 21:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@tcjennings