On 10/09/13 20:00, Adriano dos Santos Fernandes wrote: > 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.
Certainly. No difference between engine/client here when reading tables. > ISQL is full of duplicate code to handle different ODS. And it's still > bug, requiring more and more copy-past-and-adjust code. Must say I like removing duplicated code :) > I propose we start in 3.0 to do this. IMO isql is not critically important part of our code (most of users prefer various GUI), but if one has time to make isql better - certainly I see no problems with it. > 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. If (for example) when asked about list of packages it will show empty one this will be _very_ good compromise. ------------------------------------------------------------------------------ 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
