Subject Re: [firebird-support] Avoiding pessimistic locking
Author Daniel Rail

At October 7, 2005, 4:04 AM, Dmitry Sibiryakov wrote:

> On 7 Oct 2005 at 7:40, Kjell Rilbe wrote:

>>One problem that has to be dealt with:

> Actually, the problem is a matter of authority. Why all A, B and C
> are allowed to edit the same record? Who has "more right"
> information?

Here's my current real life scenario for an eye exam:

1. The technician started the eye exam with the patient, and started
entering data.
2. The optometrist continues the eye exam on the same computer.
3. The technician goes on another computer to continue to enter data
for the same eye exam, while the optometrist is still going through
the eye exam with the patient.
4. The optometrist finishes the exam with the patient and closes the
eye exam form.
5. The technician completes the eye exam form, but do note that it's
the same exam form that she opened in (3).

It's our first customer that uses our application this way. And, I'm
currently thinking of using an object persistent framework where any
data changes would be immediately saved to the database, inside a
short transaction. But, I will also need to query the database on a
regular interval for any data update that pertains with the eye exam
that is being edited.

Best regards,
Daniel Rail
Senior Software Developer
ACCRA Consultants Inc. (
ACCRA Med Software Inc. (