Version 1.5 does not work for PostgreSQL users

tolmi,

The test to know whether a node is protected uses db_affected_rows() which always returns 0 on a SELECT. (which makes sense since SELECT does not affect anything... and of course, MySQL has the opposite problem which is at times it returns 0 when you do an UPDATE which does not affect a row because the values are the same...)

Anyway, there are many different solutions, the one I propose is in the attached patch. Without that patch, the module is not functional in PostgreSQL (i.e. it looks like the node is not protected even though there is a row there and when updating you get an SQL error saying that the row already exists and thus you cannot INSERT INTO.)

Thank you.
Alexis Wilke