Thanks for the instructive information.

> For my opinion, there is a pitfall in Firebird: Due to the
> multigeneration architecture, updated, deleted and rolled back record
> versions still remain in your database file. The space, they are
> consuming, can be freed automatically in later transactions. This
> requires, that the oldest transaction number is higher than the
> transaction number of the the transaction that performed the update,
> delete (or roll back) operation before. Be aware, that you keep the
> oldest transaction number and the next transaction number close
> together. This is a question of your application design.

Do you know where I can find more details about this?

--
Geert Bevin Uwyn
"Use what you need" Lambermontlaan 148
http://www.uwyn.com 1030 Brussels
gbevin@... Tel & Fax +32 2 245 41 06