Home Dashboard Directory Help
Search

optimistic concurrency error with datetimeoffset fields upon update by d4e666


Status: 

Closed


1
0
Sign in
to vote
Type: Bug
ID: 766419
Opened: 10/6/2012 6:23:28 AM
Access Restriction: Public
1
Workaround(s)
view
0
User(s) can reproduce this bug

Description

in my database I have added 3 datetimeoffset(7) fields to record when a record is inserted, updated or deleted. All fields are nullable but date inserted and date updated are set to thefaultvalue getutcdate(). Every time I want to save a record in SSMS I get the notification that data has changed. This seems unlikly since

1. I am the only user on the database
2. The database is local to my system
3. I get this on overy record which seems rather unlikly that someone else is changing my data
Details
Sign in to post a comment.
Posted by Microsoft on 2/6/2013 at 11:51 AM
Hi!, thanks for writing in to Microsoft and reporting this bug.

We took a look at this bug and triaged it against several others and unfortunately, it did not meet the bar to be fixed. While we are closing this bug as 'won't fix', we have taken note of this internally and we will try & incorporate this request when we revisit this functionality in a future release of SSMS.

Regards,
Sanjay Nagamangalam, SQL Server Manageability
Sign in to post a workaround.
Posted by d4e666 on 10/6/2012 at 6:24 AM
convert all datetimeoffset fields to datetime2 fields for the moment. This only matters when I start deploying my application worldwide