Yes, I am the only connected, I had did that in my own computer, nobody more
is connected.

I think the problem was:
- I had deleted some rows before I had added the new column and therefore
before the new primary key.

Maybe in some dark corner the deleted rows (which doesn't had the IDENTI
column when deleted) still exists.

Greetings.

Walter.

On Fri, Jul 22, 2011 at 2:53 AM, Thomas Steinmaurer <ts@...>wrote:

> **
>
>
> > The table had another rows before, but I had deleted them and commited. I
> > had added new rows and commited.
> >
> > That can be the problem?
>
> My test was with existing records, so if you have declared the third
> field as NOT NULL, committed this change, inserted values into this new
> field, committed that as well, then the new primary key constraint
> should work fine.
>
> Are you the only one connected to the database when doing this change?
>
>
> > By the way, I'm using version 2.5
>
> My test ran with 2.1.4 and 2.5.0 just fine.
>
>
> --
> With regards,
>
> Thomas Steinmaurer
> Upscene Productions
> http://www.upscene.com
> http://blog.upscene.com/thomas/
>
> Download LogManager Series, FB TraceManager today!
> Continuous Database Monitoring Solutions supporting
> Firebird, InterBase, Advantage Database, MS SQL Server
> and NexusDB!
>
>
>


[Non-text portions of this message have been removed]