On 24 April 2012 11:52, <jegaza@...> wrote:

> **
>
>
> El , Nick Upson <nu@...> escribió:
>
> > Hi,
> > from the docs I have read I should be able to alter an SP, even though
> > another process is running it (using firebird 2.1 I know this was an
> issue
> > in 2.0)
> > yet doing so from db workbench I get the following output,
> > lock conflict on no wait transaction
> > unsuccessful metadata update
> > object PR_XX is in use
> > while executing:
> > ALTER PROCEDURE PR_XX ......
>
> You can do it in superserver, classic/superclassic blocks metadata changes
> while there is one connection using it.
>
> Jesus
>

Thanks, I hadn't considered it might vary by classic/SS,

any idea how I can identify the blocking connection? (is this case there
should be none)


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