How can we help you today? How can we help you today?

DateTimeOffset comparisons have been broken again

I have just updated to 15.4.10.27977 and datetimeoffset comparison and deploys have been broken. The actual date in my database is “2024-11-29 08:28:05.5656347 +11:00”, but the comparison is trying to deploy “2024-12--01 08:28:05.5656347 +11:00”. Has there been a regression in how leapyears are handled?

Phil
0

Comments

2 comments

Sort by
  • Jon Kirkwood
    Official comment

    Hi Phil, 

    Thanks for reaching out on the Redgate forums regarding your SQL Data Compare concern. 
    I've looked through and couldn't see any explicit changes that may have been connected to this datatype.

    Doing some testing I wasn't able to trigger anything immediate to show an issue - do you have an example that you are able to share to help replicate this if it is indeed a bug/regression that needs to be escalated.

    We do have some releases since 15.4.10, it may be worth patching to see if this is resolved already. 
    Download link for V15.4.12 can be found here:
    https://download.red-gate.com/checkforupdates/SQLDataCompare/SQLDataCompare_15.4.12.28089.exe

     

    Jon Kirkwood
  • Jessicabuckley219

    I think there might be a bug in the DateTimeOffset comparison after your update, possibly related to how leap years or time zones are handled. Try checking if there are any new patches or updates available. Also, verify that your system and database time zones are correctly set. If the issue persists, consider manually adjusting the comparison logic or rolling back to a previous stable version.
     

    Jessicabuckley219
    0

Add comment

Please sign in to leave a comment.