At 01:39 PM 19/07/2004 +0000, you wrote:

>Hi,
>
>--- In IBObjects@yahoogroups.com, "Mihai Chezan" <gsmcq@y...> wrote:
> > Not sure if I understand your question, but you could put the
>master
> > and the detail in the same transaction.
>
>all detail queries have the same transaction as the master query. But
>when I change the data in one of the detail queries i have to comit
>the transaction in order to see the changed data in the master query.

Transactions can "see" all of their own uncommitted work. If, however, you
have a *computed* column in the master that accrues values from the
details, you won't see that in the application until after the commit,
because computation occurs at SELECT and SELECT won't perform a dirty read.

Can you provide an example of what you observe and explain what you expect.

In response to your original question, Firebird/IB do not support nesting
one transaction within another. Firebird 1.5 has the SAVEPOINT mechanisms
implemented in SQL. See the Fb 1.5 release notes for doc.

Helen