> Roman, this code seems incorrect to me. Firebird complies with
> SQL200X standard and "RELEASE SAVEPOINT" statement invalidates
> mentioned savepoint and all savepoints set after it (see the docs).
> This is not something that JDBC specifies.
>
> So I'd recommend you to use Firebird extension here:
> + mc.executeImmediate(
> + "RELEASE SAVEPOINT " +
> + fbSavepoint.getServerSavepointId()+ "
> ONLY" );

Ok, I will fix this.

> Another issue. I suppose that server exceptions need to be avoided
> only for unnamed savepoints (because users are not expected to see
> driver-internal savepoint names). To avoid them actually, you need
> to invalidate unnamed savepoints at the end of transaction.

You mean that I should not invalidate named savepoint at all in favor
of server exception? But if I have to track unnamed savepoints, I can
also track named savepoints too and invalidate them all on tx
commit... What do you think?