01.09.2013 06:29, Ann Harrison wrote: > I think this is correct - if unexplicable - behavior according to the > Standard. Something about the state of the column prior to the operation.
I respectfully disagree. The NEW context is in the perfectly valid state in the BEFORE INSERT triggers. If you can evaluate both NEW.FIELD and an explicit expression based on that field, why you cannot evaluate a computed field based on the same expression? It worked fine in all IB/FB versions and the ticket is about the regression introduced recently. Dmitry ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
