Subject | Re: Explicit table lock |
---|---|
Author | Ed Dressel |
Post date | 2004-05-18T17:22:36Z |
--- In firebird-support@yahoogroups.com,
franciscojose.ruedacastanon@t... wrote:
will allow the report to view only the information inside of the
transaction--any other reports will not have access ot the data until
the transaction is committed (before which point, as suggested
elsewhere, delete the data).
Ed Dressel
franciscojose.ruedacastanon@t... wrote:
> Let me explain what I'm trying to achieve; I'm new toFirebird and
> I've not very clear this point.tables of
>
> I have several tables that gather information from the main
> database when a report is launched. In this process, first all therecords
> are deleted, then the new ones are inserted and finally severalfields are
> updated from other tables. Each of these actions is performedinside a
> transaction (so, there are three transactions). My doubt is: ifduring this
> whole process another user launches the same report with otherparameters,
> what will be the final state of the table? Maybe there will bea "mix" of
> records of the several requests? So the idea is to isolate the wholeand to
> process of generating the report when the first user launches it
> "lock" the other users while the process is running.change it to perform all writes/reads inside of one transaction. This
will allow the report to view only the information inside of the
transaction--any other reports will not have access ot the data until
the transaction is committed (before which point, as suggested
elsewhere, delete the data).
Ed Dressel