I came across a bit of a glitch in using timestamps for checking concurrency violations in LINQ to SQL and thought I'd share. Say I've got a table like;create table Person
(
id int identity primary key,
firstName nvarchar(30),
lastName nvarchar(30),
Read More