-
Notifications
You must be signed in to change notification settings - Fork 8
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
[Issue #1686] add created_at
, updated_at
, and deleted_at
columns to staging tables
#1894
[Issue #1686] add created_at
, updated_at
, and deleted_at
columns to staging tables
#1894
Conversation
…s to staging tables
api/src/db/migrations/versions/2024_05_01_add_created_at_updated_at_and_deleted_.py
Outdated
Show resolved
Hide resolved
command.downgrade(alembic_cfg, revision) | ||
|
||
|
||
def enable_query_logging() -> None: |
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.
Testing this, it ends up being very verbose. Is there a way we could make this configurable? Fine if its a follow-up, but locally I want to see just the alembic output, not this so much and now the logs are 3x as long
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.
The goal is that if there's ever a very slow migration, you can see which one it's currently processing. I'll make a follow up.
Co-authored-by: Michael Chouinard <46358556+chouinar@users.noreply.github.com>
Summary
Part of #1686 (separate for easier review)
Time to review: 2 mins
Changes proposed
created_at
,updated_at
, anddeleted_at
columns to staging tablesContext for reviewers
These columns will provide helpful metadata for understanding or troubleshooting the load process.
The
created_at
andupdated_at
columns are set automatically by SQLAlchemy.For
deleted_at
, I will update #1852 after this is merged.Additional information
Example from local testing: