Add temporal tables and rework insert statements #391
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
marcellmueller
force-pushed
the
spike/postgres-update-versioning
branch
8 times, most recently
from
0abe397 to
7a04c0f
Compare
marcellmueller
force-pushed
the
spike/postgres-update-versioning
branch
from
ef454d9 to
44e46e1
Compare
marcellmueller
changed the title
marcellmueller
force-pushed
the
spike/postgres-update-versioning
branch
from
d766465 to
68c32c4
Compare
marcellmueller
force-pushed
the
spike/postgres-update-versioning
branch
from
2f9850f to
6acd9e7
Compare
marcellmueller
force-pushed
the
spike/postgres-update-versioning
branch
from
6acd9e7 to
6432939
Compare
marcellmueller
force-pushed
the
spike/postgres-update-versioning
branch
5 times, most recently
from
caa90c9 to
daacabf
Compare
marcellmueller
force-pushed
the
spike/postgres-update-versioning
branch
from
4bf8212 to
c63c4f7
Compare
marcellmueller
force-pushed
the
spike/postgres-update-versioning
branch
3 times, most recently
from
b932706 to
e2bb445
Compare
marcellmueller
force-pushed
the
spike/postgres-update-versioning
branch
from
4738e62 to
d94bd08
Compare
jimmypalelil
approved these changes
Mar 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
#308
upsert_timestamp_columnsutil function to streamline adding metadata columns iecreated_at, created_by, updated_at, updated_bycolumns to a tablesetup_temporal_tableutil function which adds a_historyversion of the table and updated_if_changed trigger function on a table_codetables only haveupdate_timestampin the FTA database, noupdated_useridor created metadata so I've kept it the same. I'm split on if adding history tracking to these tables is useful, I've added history tables to them for now.Tested with
flyway cleandisabled for the RST migrations. No new records are added on a redeploy to a steady database, and if we make some changes to the FTA data then that was updated, with history being tracked in the history table.