Set created_at and updated_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 the created_at and updated_at fields rather than relying on the table default of current_timestamp.
current_timestamp is the same for all statements in a transaction, which causes problems when ordering statements by created_at.
Set
created_atandupdated_atexplicitly 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_atandupdated_atfields rather than relying on the table default ofcurrent_timestamp.current_timestampis the same for all statements in a transaction, which causes problems when ordering statements bycreated_at.Fixes #361