Conversation
|
Seems like the SQL Server 2022 fails due to a problem with datatypes. Was the CI DB backends changed? |
Could be something changed in the workflow that starts the instance (not our workflow). |
I just check our local MS SQL Server Version 15.00.4375 and it provides the expected datatypes. A guess is that the CI version uses DATETIME2 instead of DATETIME - the latter is sufficient for our purpose. |
|
Could also be an update to SQL Server 2022 |
SofiaOtero
left a comment
There was a problem hiding this comment.
Approved, but support of SQL Server 2022 should be added in a future PR.
At random update_snapshot hangs after writing "After to_add". This is issue #191
Intent
Solves issue #191
Additional log_info output is adjusted to reduce lines that comes after almost zero computation time.
Approach
The issue was resolved by adding a compute of currently_valid_checksums.
Known issues
N/A
Checklist
NEWS.md