>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.

Just a silly question from me to rule out the obvious: You have checked that both the remaining generators and the missing DDL is executed within the same transaction, and not that you have assigned a transaction to the creation of these two generators, whereas you haven't done so to the remaining DDL? And all your DDL executes, it is not that you get some kind of error early on in the creation? If this creation fails despite all the DDL being in the same script (TIB_Script to talk IBO, don't know whether PHP has anything similar), then I'm just among the puzzled ones - it doesn't make sense that two generators remain whilst generators created before them disappears...

Set