Re: PostgreSQL and multiple database access

You could use locking for this (as someone else suggested) but you'd
probably be better off using transactions. That way no one will get an
error, and whoever commits last will have the final say of what the record
is set to.

At 05:41 PM 6/7/00, you wrote:
>Hi,
>
>I work in an environment where people can update the PostgreSQL database
>from several sites (insert, update, delete statements).
>If two people try to update, insert or delete the same row at the same
>time, or if one deletes a row that the other is viewing and trying to
>update, in postgreSQL, what happens??
>
>I'm looking from success/failure stories, tips anything that can help me
>code consequently!
>
>TIA
>
>T.J.