Best practice updating data in webapps?

From: Bjørn T Johansen <btj(at)havleik(dot)no>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Best practice updating data in webapps?
Date: 2004-11-24 11:00:30
Message-ID: 41A469CE.7050109@havleik.no
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Maybe a bit outside the scope of PGSQL but when designing webapps where different users
can edit the same record at the same time, what is the best way to solve this situation?
One way is to use an update field, that gets selected with rest of the data and when
updating the data, check this update field with the one in the db; if they don't match,
someone else has updated the record before you..
But is this the best way?

Regards,

BTJ

--
-----------------------------------------------------------------------------------------------
Bjørn T Johansen

btj(at)havleik(dot)no
-----------------------------------------------------------------------------------------------
Someone wrote:
"I understand that if you play a Windows CD backwards you hear strange Satanic messages"
To which someone replied:
"It's even worse than that; play it forwards and it installs Windows"
-----------------------------------------------------------------------------------------------

Browse pgsql-general by date

  From Date Subject
Next Message Edmund Kleiser 2004-11-24 11:18:09 select into temp tables withough using EXECUTE in plpgsql
Previous Message Najib Abi Fadel 2004-11-24 10:47:27 Re: Row creation time