IBO's terminology is a little different to the raw API transaction settings.
If you stick to IBO terminology
tiCommited provides for transactions to read all commited data and also
allows you to overwrite commited data, even if you are not looking at the
current version.
I use tiConcurrency when I also set queries to pessimistic locking. This
give me the ability to lock a record on edit, and to also be warned that
your attempt to lock is invalid since you're attempt at locking the record
will fail since you have an old version.
Alan

> -----Original Message-----
> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]On
> Behalf Of tarno_nona
> Sent: Monday, 18 June 2007 4:59 AM
> To: IBObjects@yahoogroups.com
> Subject: [IBO] Which isolation level to use?
>
>
> Hi all,
>
> I'm a newbie on FB and IBO, i'm still confused with isolation level to
> use in transaction. What is the best practice? Is it true that
> read_committed still allow lost update to happen?
>
> Regards
>
> Tarno
>
>
>
> __________________________________________________________________
> _________
> IB Objects - direct, complete, custom connectivity to Firebird or
> InterBase
> without the need for BDE, ODBC or any other layer.
> __________________________________________________________________
> _________
> http://www.ibobjects.com - your IBO community resource for Tech
> Info papers,
> keyword-searchable FAQ, community code contributions and more !
>
> Yahoo! Groups Links
>
>
>
>