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.
By finding catch phrases (quotes) you find the blogs that quote the news paper article.
What about specific events where there isnt a catch phrase, wouldnt those be excluded by the way the matching works?
...err, I mean. Isn't this old news?
I though Europe was blocked 2 years or so earlier. Didn't know that France was an exception. Or he was lucky with his IP block being considered American.
Being in Australia i was blocked off 1-2 years ago.
I think the OP was just in a lucky IP range which they finally fixed up.
Well I'm qualified as one
He used et al - he must be a lawyer
From IMDB:
Country - Date
Germany - 11 December 2008
UK - 12 December 2008
Brazil - 25 December 2008
Iceland - 26 December 2008
Life is a healthy respect for mother nature laced with greed.