Re: [Firebird-test] Firebird does not create unique constraint.

[Leyne, S. <Se...@br...>]

Mike,

> Leyne, Sean wrote:
> > A Firebird index includes index data for all active transactions,
this
> > is by design.
> >
> > Accordingly, what you are seeing is the correct behaviour.
> >
> >
> > Sean
> >
> I know that. The question is why there were active transactions
> affecting the new index.

Because a unique index requires that the engine consider both committed
transactions and also active transactions, in order to ensure
uniqueness.

You will note that the uniqueness error is noted when the insert/update
takes place, not when the transaction is committed.  Accordingly, the
index/engine is affected by active transactions.

>I don't think this is a new issue. See CORE-400
> <http://tracker.firebirdsql.org/browse/CORE-400> in bug database.

This case is not applicable -- it involves restoring a database which
now has a unique constraint but which has data which isn't unique.  This
is a restore problem.


> I have a copy of the database running on FB 1.5 and the same operation
> went through fine there.

Unless you had active transactions, I would have expected the same but
you didn't so the comparison is not equivalent.

Regards,

Sean