Subject RE: [IBO] Full Table Lock?
Author Kaputnik
One solution I have already seen in the past is to start a nice long
transaction with Concurrency (not read committed) and go through the
delivery notes one by one. As soon as you create an invoice, update the
delivery note (set a flag or so) to reflect its invoice was created and do
your stuff. Updating the delivery note and keeping the transaction open will
lock this note for further updates and no other app will be able to create a
new invoice based on this note. If e.g. you put the invoice-creating process
into a stored procedure, this can first update the note and then create the
inovice and issue a meaningfull exception if the update fails.
Another possible solution is to use a temporary buffer for the delivery
notes. As soon as the note was handled for invoice-generation, move the
record out of the table and into a the final table.


Nick Josipovic

BIT Institute
Prof. Dr. Franz Steffens
University of Mannheim
T: ++49 621 181 1621
M: ++49 179 133 44 16
S: ++49 621 181 1622
F: ++49 621 181 1618

> -----Original Message-----
> From: Salva [mailto:elsalvavidas@...]
> Sent: Wednesday, February 13, 2002 6:55 PM
> To:
> Subject: [IBO] Full Table Lock?
> Hello,
> I'm converting an application from DB7 to IBO. It has a very delicate
> process, calculate invoices from previous delivery notes.
> As one invoice is created from with 1 or more delivery notes only one user
> can fire this process at a time. In DB7 I full locked
> temporal tables, and that it is, only one user can fire the process.
> Any idea of doing the same with Interbase? (I'm newby in C/S and
> InterBase).
> Thank's Salva.
> __________________________________________________________________
> _________
> IB Objects - direct, complete, custom connectivity to Firebird or
> InterBase
> without the need for BDE, ODBC or any other layer.
> __________________________________________________________________
> _________
> - your IBO community resource for Tech
> Info papers,
> keyword-searchable FAQ, community code contributions and more !
> Your use of Yahoo! Groups is subject to