Subject | RE: [ib-support] Edited Stored Procedure not taking place. |
---|---|
Author | C Fraser |
Post date | 2002-11-06T23:50:41Z |
Arr...
Just found that by changing the trigger that calls the stored procedure,
it all of a sudden started to use the new stored procedure.
Very confusing... I guess the trigger somehow keeps a link to the old
procedure??
Just tried changing the stored proc again, and indeed, without changing
the trigger, the old one still gets called, change the trigger (to be
the same) and hey presto, the new stored proc gets called.
Regards
Colin
-----Original Message-----
From: C Fraser [mailto:Colin.Fraser@...]
Sent: Thursday, 7 November 2002 12:47 p.m.
To: ib-support@yahoogroups.com
Subject: RE: [ib-support] Edited Stored Procedure not taking place.
Hi Thomas, thanks for your prompt reply :-)
Do all the clients need to disconnect for the DB to use the new
procedure?
I did disconnect all the apps on my PC from the DB after making the
change, then restarted the app, logged on and the old procedure still
executed.
(Just tried it again (even rebooted), and the old procedure is still
being executed.)
Regards
Colin
-----Original Message-----
From: Thomas Steinmaurer [mailto:ts@...]
Sent: Thursday, 7 November 2002 10:16 a.m.
To: ib-support@yahoogroups.com
Subject: RE: [ib-support] Edited Stored Procedure not taking place.
Hello Colin
other connections.
stored procedure.
Regards,
Thomas Steinmaurer
IB LogManager 2.1 - The Logging/Auditing Tool for InterBase and Firebird
http://www.iblogmanager.com
To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
######################################################################
Attention:
The information in this email and in any attachments is confidential.
If you are not the intended recipient then please do not distribute,
copy or use this information. Please notify us immediately by return
email and then delete the message from your computer.
Any views or opinions presented are solely those of the author.
######################################################################
To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
######################################################################
Attention:
The information in this email and in any attachments is confidential.
If you are not the intended recipient then please do not distribute,
copy or use this information. Please notify us immediately by return
email and then delete the message from your computer.
Any views or opinions presented are solely those of the author.
######################################################################
Just found that by changing the trigger that calls the stored procedure,
it all of a sudden started to use the new stored procedure.
Very confusing... I guess the trigger somehow keeps a link to the old
procedure??
Just tried changing the stored proc again, and indeed, without changing
the trigger, the old one still gets called, change the trigger (to be
the same) and hey presto, the new stored proc gets called.
Regards
Colin
-----Original Message-----
From: C Fraser [mailto:Colin.Fraser@...]
Sent: Thursday, 7 November 2002 12:47 p.m.
To: ib-support@yahoogroups.com
Subject: RE: [ib-support] Edited Stored Procedure not taking place.
Hi Thomas, thanks for your prompt reply :-)
Do all the clients need to disconnect for the DB to use the new
procedure?
I did disconnect all the apps on my PC from the DB after making the
change, then restarted the app, logged on and the old procedure still
executed.
(Just tried it again (even rebooted), and the old procedure is still
being executed.)
Regards
Colin
-----Original Message-----
From: Thomas Steinmaurer [mailto:ts@...]
Sent: Thursday, 7 November 2002 10:16 a.m.
To: ib-support@yahoogroups.com
Subject: RE: [ib-support] Edited Stored Procedure not taking place.
Hello Colin
> I have just edited a stored procedure (about 10 minutes ago) and itYes it is normal, because BLR of stored procedures is cached for all
> clearly is not being used yet.
>
> I can disconnect from the db, go back into it and verify that the
> stored procedure code has been updated, but the actions being
> performed by other applications when executing the stored procedure
> clearly show that old version of the stored procedure is being
> executed.
>
> First question is, is this normal? Something to-do with transactions
> perhaps?
other connections.
> And the next question is how do I get my new stored procedure to beThe other clients must reconnect to see the compiled changes of the
> used?
stored procedure.
Regards,
Thomas Steinmaurer
IB LogManager 2.1 - The Logging/Auditing Tool for InterBase and Firebird
http://www.iblogmanager.com
To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
######################################################################
Attention:
The information in this email and in any attachments is confidential.
If you are not the intended recipient then please do not distribute,
copy or use this information. Please notify us immediately by return
email and then delete the message from your computer.
Any views or opinions presented are solely those of the author.
######################################################################
To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
######################################################################
Attention:
The information in this email and in any attachments is confidential.
If you are not the intended recipient then please do not distribute,
copy or use this information. Please notify us immediately by return
email and then delete the message from your computer.
Any views or opinions presented are solely those of the author.
######################################################################