Yes, tanks Helen. I realize that I can start a new read commited transaction at ISQL, then the commited transactions will be visible. By the way, what is the default transaction in ISQL?

Dufloth.

----- Original Message -----
From: Helen Borrie
To: ib-support@yahoogroups.com
Sent: Saturday, March 09, 2002 11:49 AM
Subject: Re: [ib-support] Transaction and visibility


At 11:34 AM 09-03-02 -0300, you wrote:
>Hi. I using Delphi 6 with DBExpress, and making some insertions and
>commiting at database ( FB 1 rc2 WinXP ), other client connected (isql)
>don't see this insertions until I reconnect with database (isql). The
>transaction of app that make the insertions is set to readcommited. The
>other client, isql in this case, wouldn't have to see my insertions? What
>kind of transaction is more approprieted to make this? (other clients
>[transactions] to see commited transactions without reconnection)

DBXpress is very "bare bones" with respect to refreshing the user's
view. You have to call Close and Open on the dataset to get the latest
view of committed work.

ReadCommitted isolation lets one transaction see the effects of others'
changes. It won't affect the transaction actually performing the insert,
since it can already see its own work. Other transactions will have to be
in ReadCommitted isolation too, in order to see those inserts; otherwise,
only starting a new transaction would make the new rows visible.

H.



All for Open and Open for All
Firebird Open SQL Database · http://firebirdsql.org ·
http://users.tpg.com.au/helebor/
_______________________________________________________


Yahoo! Groups Sponsor
ADVERTISEMENT




To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



[Non-text portions of this message have been removed]