Not sure that this is a bug, a stored procedure is a shared compiled
executable, when you modify a stored procedure don't expect the server to
pick up the new version, jsut because it has been modified. Some database
objects, modified stored procedures especially, only become available for
use when the previous version of the stored procedure is no longer in use.
You would need to disconnect from the database and re-connect before the old
procedure was marked as no longer in use and the new modified procedure is
available for use.

Hence the re-boot, doing the same, but somewhat over kill, job for you.

Regards
Paul Beach
Main Tel (UK):+44 (0) 1844 354465
Mobile: (UK): +44 (0) 7764 188603
http://www.ibphoenix.com
For all your upto date Firebird and
InterBase information

----- Original Message -----
From: Paul Poulain <paul@...>
To: <ib-support@yahoogroups.com>
Sent: Thursday, October 11, 2001 10:13 AM
Subject: [ib-support] YAB ? (Yet Another Bug)


> Hi,
>
> I've a DB with firebird (recent build). The admin front end is QuickDesk
> 1.7.10.14.
> The table COMMAND has a after-insert trigger that insert a line into a
> MOVEMENT table for the accounting process.
> This trigger calls a stored proc.
>
> It works fine.
>
> Yesterday, I added a column in the MOVEMENT table and modified the strored
> proc accordingly. The column is a copy of a COMMANDE-column.
>
> Surprised : the column is always NULL.
>
> Made a mistake ? No, the code seems OK. So, I try to call the stored proc
> 'by hand' : Works fine...
>
> Mhhhhh... strange very strange.
>
> Maybe a /init.rc/firebird restart ???
>
> Oh yeah, it works perfectly fine now.
>
> Can someone give me an explanation ?
>
> Paul
>
>
>
> 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/
>
>
>