Doesn´t work.

The only way I found to alter a stored procedure in FB 2.5.2 , windows 64, SuperClassic is closing all conections and restarting the FB service.

Hugo

Em 18/08/2014 16:55, 'Carlos H. Cantu' [email protected] [firebird-support] escreveu:

Try to set the DDL transaction mode in Expert to WAIT instead of NO WAIT and see what happens.

Carlos
Firebird Performance in Detail - http://videos.firebirddevelopersday.com
www.firebirdnews.org <http://www.firebirdnews.org>- www.FireBase.com.br <http://www.FireBase.com.br>


        


Hello Carlos.

Thanks.

I am using IBExpert to run an 'CREATE OR ALTER PROCEDURE MY_PROCEDURE....."

That´s why I am not understending what can avoid to execute this.

This PROCEDURE just returns a value from a table.

I should be able to drop and insert a PROCEDURE at anytime into the DB. Should not I?



Em 18/08/2014 16:40, 'Carlos H. Cantu' [email protected] <mailto:[email protected]>[firebird-support] escreveu:

When you start a transaction you determine the wait mode. Where you set this depends on the component/access technology you are using.

Carlos
Firebird Performance in Detail - http://videos.firebirddevelopersday.com
www.firebirdnews.org <http://www.firebirdnews.org>- www.FireBase.com.br <http://www.FireBase.com.br>


        



Hi Carlos.

Where do I chage it?

Hugo

Em 18/08/2014 15:06, 'Carlos H. Cantu' [email protected] <mailto:[email protected]>[firebird-support] escreveu:

To avoid such error, try to change the DDL transaction parameter to
WAIT instead of NO WAIT.

Carlos
Firebird Performance in Detail - http://videos.firebirddevelopersday.com
www.firebirdnews.org <http://www.firebirdnews.org>- www.FireBase.com.br <http://www.FireBase.com.br>

HEhmcfs> Hello.

HEhmcfs> IBExpert shows the message:

HEhmcfs> lock conflict on no wait transaction
HEhmcfs> unsuccessful metada update
HEhmcfs> object MY_PROCEDURE is in use

HEhmcfs> How can I see 'who' is using the procedure?


--


Atenciosamente,

Hugo Eyng



--


Atenciosamente,

Hugo Eyng




--


Atenciosamente,

Hugo Eyng

Reply via email to