LINQ in Action roller

Trying to understand the advantage of LINQ's "Update Check" always vs when changed values.

Each column in LINQ tables have property called " Update Check " for optimisitc concurrency. Any real benefit of choosing Always vs When Changed? Seems that if you choose "Always" it will be a performance drag b/c regardless of which field is changed on the table, any fields where "Update Check=Always" will always have to validateĀ if a concurrency issues exist. Its almost better to choose "When changed" instead of Always correct right? If not please explain... Thanks! Read More...
Published Monday, October 13, 2008 12:39 AM by MSDN Forums: LINQ Project General
Anonymous comments are disabled

Featured Item

This Blog

Sponsoring

Syndication