> Duncan was referring to IBO's Savepoint method, not the SQL SAVEPOINT
> statement. This is a client-side method (that predates Firebird's
> SAVEPOINT syntax by about 6 years), that allows you to perform a
> CommitRetaining on all work so far posted for a transaction. So

IBO's

> Savepoint method indeed creates one record version for each record it
> updates; and it also enables the user to go back and do more updates

on

> these records, thus propagating more record versions that won't get
> garbage-collected.
>

Ah, makes sense in that context then. Sounds to me like something to
avoid (especially considering real savepoints are available in Firebird
1.5+).

Adam