On Thu, 2006-02-09 at 06:08 +0000, muthu_krishnans wrote:

> Is there a way do disable the MVCC and force the FB engine to behave
> like a other DBs in the locking front.

Fb is going to behave as a proper RDBMS should as per spec, and design.
However there are a few transaction related configuration options.

If you do not already have it, download the InterBase 6 beta docs.
Specifically the API guide and check out Chapter 5, Transactions.
http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_download_documentation

> i.e., if a write lock for a
> record is given to a transaction, let the other transaction which
> needs the write lock for the same record to wait till the first
> transaction is completed(Commit/Rollback).

Most likely need to be uses isc_tpb_wait, to wait to see if a
conflicting transaction is rolled back. If it is retry, if not, fail
with conflicting updates/deadlock.

However it sounds mostly like some changes might need to take place in
your applications logic and functionality. Typically easier to modify an
app around a db, than a db around an app. More so if the app was
designed and used with another db. Not providing the same feature set,
an etc.

--
Sincerely,
William L. Thomson Jr.
Obsidian-Studios, Inc.
http://www.obsidian-studios.com