Distinguish inferred migrations by timestamp for statements within the same transaction #362
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.<
2D82
/span>
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.
Set
created_at
andupdated_at
explicitly when inserting inferred migrations into the migrations table.When two statements are run in a transaction, we need to explicitly insert
statement_timestamp()
into thecreated_at
andupdated_at
fields rather than relying on the table default ofcurrent_timestamp
.current_timestamp
is the same for all statements in a transaction, which causes problems when ordering statements bycreated_at
.Fixes #361