🚀 go-pugleaf

> OK but I encounter today a very strange scenario:
> first after I modified my stored procedure I run Delphi to see what will
> go, I set before 3 triggers (after insert, after update and after
> delete) for "table a" which they all call one procedure with different
> parameters
>
> then when I try to post an inserted record I get exception error that I
> try to post a null value to a none null field The big surprise is that
> field is not in "table a" I insert the record into but in another table
> "table b" which I only touch it with the update statement and "table a"
> has foreign keys on table "table a"
>
> after alot of going around my self I deactivate the trigger which call
> the procedure then I  tried again to insert  the record and it is
> inserted normally so reactivate the trigger and try again to insert the
> record *without any change in the sql* the record inserted with the same
> data I tried before without any error !!!!!!!!!
>
> can you explain that phenomena ??

Metadata caching on the server side by the IB Server process.

By re-activating the trigger, you're causing that part of the cache
to get flushed. IB will re-load the metadata of the trigger and
procedure from the database and load the new code.


-- 
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle &
MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com