The old system i dont believe was broken. It gave me the privacy settings that i wanted.
Given it might be a bit confusing for novice users, but all they needed to give it was an interface facelift.
Right now i have less privacy than i had - i cant hide any comments/likes i make on the system and need to go through and individually delete them off my wall.
What he's saying is it is his customers (advertisers not users) want less privacy, so they can target ads more profitably.
Thanks to overbaud's reply below. By hash i was meaning a solution such as guid value. I was speaking generically and not taking the literal meaning of hash for the purpose of being database agnostic.
Create a timestamp/random hash and store it against each record, then include it in your update query.
UPDATE table SET
data1 = @Data,
hash = NewHash()
WHERE ID = @ID
AND Hash = @Hash
Every save, change the hash to a new value.
If someone has changed the record and another person goes to save it, the hash wont match and 0 records will be updated. This can then be captured in your web application.
If 0 records updated - display error saying "user has already changed record, please reload page"
If 1 records updated - display success.
Arithmetic is being able to count up to twenty without taking off your shoes. -- Mickey Mouse