> Step 3 works fine, but when you extract the DDL of the table and try to run > it, > it will crash, since it will be extracted like: > > CREATE TABLE A ( > FIELD2 NUMERIC(9,2), > FIELD1 COMPUTED BY (field3 * 0.5), > FIELD3 NUMERIC(9,2) > );
Actually, that points out a problem with the extract logic/procedure more than with the engine/parser. The DDL extract should be processing computed fields after 'real' fields. It is relatively simple to determine whether a field is computed or real. But I see that even IBExpert does not apply this logic. Sean ------------------------------------------------------------------------------ How fast is your code? 3 out of 4 devs don\\\'t know how their code performs in production. Find out how slow your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219672;13503038;z? http://info.appdynamics.com/FreeJavaPerformanceDownload.html Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
