Thank you for your answer Karol.

I don't use FlameRobin, I'll do it now.

Greetings.

Walter.





On Mon, Jan 7, 2013 at 6:07 PM, karolbieniaszewski <
liviuslivius@...> wrote:

> **
>
>
>
>
> --- In firebird-support@yahoogroups.com, W O wrote:
> >
> > Hello everybody
> >
> > I have some doubts about delta rows.
> >
> > Transaction 510 inserts a row with this values (ID=2500,
> > LASTNAME='Kennedy', FIRSTNAME='John', SALARY=28000)
> >
> > Transaction 510 commits
> >
> > Transaction 526 updates that row with this values (ID=2500, SALARY=31000)
> >
> > How are in the database the rows now?
> >
> > 1. TRANSACTION=510, ID=2500, LASTNAME='Kennedy', FIRSTNAME='John',
> > SALARY=28000
> > TRANSACTION=526, SALARY=31000
> >
> > 2. TRANSACTION=526, ID=2500, LASTNAME='Kennedy', FIRSTNAME='John',
> > SALARY=31000
> > TRANSACTION=510, SALARY=28000
> >
> > 3. Another way
> >
> > After transaction 526 commits, how are in the database the rows? Same as
> > before the commit or different?
> >
> > Which of the rows is called the "delta" row?
> >
> > Greetings.
> >
> > Walter.
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
> Hi,
>
> All stay same as before commit but engine know that 536 is most recent
> committed transaction and if you try select then garbage collector decide
> that this old record version can be removed
>
> you have many questions about transactions but the best is do own tests.
> Run 3 times flamerobin start transactions and test what happened
>
> regards,
> Karol Bieniaszewski
>
>
>

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