I think we already reached a point where core developers can hit the hammer in what will be the chosen "solution" of this problem in FB 3. I would be satisfied with either relaxing rules in rdb$triggers/procedures, or with new syntax, or with last Jim's proposal of SET statement. I'll leave this to you (core developers) decide what one is more adequate for the time being.
Another option (maybe not so simple) could be a flag in the database header that would tell Firebird if the source should be kept or not. The flag could be set with gfix, as we already do with forced writes, etc. About the other proposals, they can be discussed again for future releases, after FB 3 is finally out. []s Carlos http://www.firebirdnews.org FireBase - http://www.FireBase.com.br ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
