It is strange, because I disconnect and connect again and the problem
continues.

I had commited after each step.

And all rows have a value on the IDENTI column.

Greetings.

Walter.

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

> **
>
>
> > 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.
>
> Perhaps a matter of transaction isolation level. If you ran your thing
> in two transactions. The one transaction doing the deletes and possibly
> using a snapshot isolation transaction for the DDL stuff. I don't know.
>
>
> --
> 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]