Hi! Since Firebird 2.1.2, engine and client tools with embedded (GPRE) SQL may access non-existent system fields, which are then resolved to NULL.
This ability, for the internal engine code, allowed better (short, faster) code in 2.5, where the server had the support for older ODS. But so far, we did not used the techniquefor good in the client. And in most cases, the correct interpretation for non-existent fields in ISQL is to treat them as NULL. ISQL is full of duplicate code to handle different ODS. And it's still bug, requiring more and more copy-past-and-adjust code. I propose we start in 3.0 to do this. Of course, ISQL from 3.0 will not fully work when connected to 2.1.1 and elder servers, but I think it's a good compromise. Adriano ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
