(seeing Ann's post)
Secondly, with versioning, you need a very, very special set of
circumstances to
need table locking. In our entire accounting system we only use it in
one place:
when we apply count totals to inventory. We need to be able to run
through the
data 3 times guaranteeing that there is not change. This is because we
also keep
detailed counts at the bin level and have to reconcile the bins, with
the location,
with the totals.

So why do you need it or do you need to learn more about versioning?

nagypapi wrote:

>I was wondering, are there any plans to implement explicit table
>locking as is in PostgreSQL:
>http://www.postgresql.org/docs/7.4/interactive/explicit-locking.html
>http://www.postgresql.org/docs/7.4/interactive/sql-lock.html
>
>This topic was more or less previously discussed in firebird-java, and
>we got to the conclusion that setting the transaction isolation level
>is a possible solution, but explicit locking seems more appropriate
>and flexible (from a java programmer's point of view)
>John
>
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
>

--
Thomas Miller
Wash DC Delphi SIG Chairperson
Delphi Client/Server Certified Developer
BSS Accounting & Distribution Software
BSS Enterprise Accounting FrameWork

http://www.bss-software.com
http://www.cpcug.org/user/delphi/index.html
https://sourceforge.net/projects/uopl/
http://sourceforge.net/projects/dbexpressplus