--- In ib-support@y..., Duilio Foschi <dedalus@y...> wrote:

> >That should have not created a deadlock at all, reads never block

writes.

>
> good to know, but that is what happened

Duilio, it depends on what we understand by "editing". If it means
we started to change data in some data-aware control, and seems Jason
supposed this, then there should'nt be lock conflict. If we posted
this changes or performed update statement but not commited yet - it
certainly should. If we commited it means edit finished.

> >What transaction isolation were you using on your insert statement?
>
> I have no idea.
>
> It must be the standard used by WISQL.

If you mean WISQL32.EXE from IB5.x kit, it is concurrency (I'm
shure) wait (if I recall right).

Best regards, Alexander V.Nevsky.