I think if your lock version is a random hash that is updated each time you write via trigger or app code, then at best someone nefarious could change that value in the form and prevent themselves from being able to update the record.
It also depends on what you're trying to achieve. For instance, if you're just trying to help coordinate people updating a wiki page so that two people don't accidentally clobber each other's updates then it's probably not a huge concern.
From a layering perspective, you can probably implement this with checks and triggers in postgres so that it's mostly transparent to the client.
It also depends on what you're trying to achieve. For instance, if you're just trying to help coordinate people updating a wiki page so that two people don't accidentally clobber each other's updates then it's probably not a huge concern.
From a layering perspective, you can probably implement this with checks and triggers in postgres so that it's mostly transparent to the client.
That said, I wouldn't bother myself ;)