Subject | Re: [firebird-support] Rollback on FB2.5 |
---|---|
Author | Milan Tomeš - Position |
Post date | 2011-06-15T10:51:11Z |
Hi,
It's not a bug, it's a feature. Generators aren't under a transaction
control. So when you get new value from generator it's reserved and is
not rolled back when you rollback the transaction.
M.
Dne 15.6.2011 12:38, Lester Caine napsal(a):
It's not a bug, it's a feature. Generators aren't under a transaction
control. So when you get new value from generator it's reserved and is
not rolled back when you rollback the transaction.
M.
Dne 15.6.2011 12:38, Lester Caine napsal(a):
>[Non-text portions of this message have been removed]
> I'm having some fun at the moment with trying to run a clean bitweaver
> install.
> So we are talking Firebird with PHP ...
>
> There is something going wrong with the generation process for the
> tables. The
> database exists and is blank, and the debug listing is showing
> everything I
> expect, without any errors, but the commit is not working so the
> tables are not
> being saved to the database. OK I need to find out why it's not
> committing, but
> the question is one relating to the rollback. AFTER the commit failed,
> two of
> the generators ARE committed to the blank database, but not the first two
> created and none of the generators have been used at this point.
>
> Any reason why these would remain after the rollback? It through me at
> first
> because my second run with the debugger on failed because these
> generators
> existed - I'd not looked since I was expecting the database still to
> be empty.
>
> This all worked fine last time I checked but I've not run a clean
> install on 2.5
> - just updated existing ones to 2.5.
>
> --
> Lester Caine - G8HFL
>
>