Subject | Re: transactions/transaction isolation level |
---|---|
Author | Alexander V.Nevsky |
Post date | 2004-05-25T17:59:54Z |
--- In firebird-support@yahoogroups.com, "martene_firebird"
<marten.ehnberg@c...> wrote:
Update With Lock, IMO this is exactly your case. For more wide
reasoning on record-level locking, where it is useful and where not
and how can be performed in different FB version, you can look at the
article
http://www.ibphoenix.com/main.nfs?a=ibphoenix&l=;PAGES;NAME='ibp_lock_recor=
ds'
Best regards,
Alexander.
<marten.ehnberg@c...> wrote:
> Hi All!MÃ¥rten, if you use FB1.5, look at Release Notes for Select For
>
> A telemarketing company has asked me to create a client/server
> application that will provide the sales-staff with telephone numbers
> so that they can call prospective customers.
>
> My application needs to select one(1) phone number from a table
> containing the phone numbers( any phone number in the table will do )
>
> Once the application has picked a phone number, that particular
> phone number should become unavailable for others(obviously I do not
> want two or more salesreps calling the same prospective customer)
>
> Any thoughts about what I need to do...?
Update With Lock, IMO this is exactly your case. For more wide
reasoning on record-level locking, where it is useful and where not
and how can be performed in different FB version, you can look at the
article
http://www.ibphoenix.com/main.nfs?a=ibphoenix&l=;PAGES;NAME='ibp_lock_recor=
ds'
Best regards,
Alexander.