List z dnia: Sat, 17 Jun 2000, :
I usually prefer the following trick for preventing long locking
times. On every
table I define a timestamp field which is updated every time the record is
written to the database. If a user edits a record (without
locking) and commit his changes
the
Hello
I was listening Your discusion. I have practical problem for which I write my
own locking system:
Personal rekords:
Name
zip
adress
Users A,B reads data from record:
John Smith
124312
Xstreet 27
Now A change zip and write all
B change adress and write
so zip is unchanged.
In pgsql I
"Pawe³ Dubin" wrote:
Hello
I was listening Your discusion. I have practical problem for which I write my
own locking system:
Now A change zip and write all
B change adress and write
so zip is unchanged.
In pgsql I can solve it by SELECT FOR UPDATE but if user A goes for caffe
during
I usually prefer the following trick for preventing long locking
times. On every
table I define a timestamp field which is updated every time the record is
written to the database. If a user edits a record (without
locking) and commit his changes
the timestamp is returned from the client
