From: Martijn T. <m.t...@up...> - 2009-12-31 06:44:46
|
Hello Dmitry, Will there be proper documentation on the format/structure (BNF?) and when will there be a tree-structured output format with more information? With regards, Martijn Tonies Upscene Productions http://www.upscene.com Download Database Workbench for Oracle, MS SQL Server, Sybase SQL Anywhere, MySQL, InterBase, NexusDB and Firebird! Database questions? Check the forum: http://www.databasedevelopmentforum.com > After thinking a little bit more about this issue, I'm pretty sure we > should not introduce any new info tag. > > Syntactically, the new plan has the same [old] format, period. Do you > know any tool that cannot handle this: > > create table T (COL int); > create index "ABC[3]" on T(COL); > select from T where COL = 0; > -- PLAN (T INDEX ABC[3]) > > ? > > Be it a legacy tool or the new one which knows about the new plan > output, it has no idea whether [val] is a part of the index name or the > new extension, so it simply has to process it as a part of the name > (string before the next comma or the next closing brace). > > What issues can you guys see here? > > Also, a point about hash joins was absolutely valid. All the extensions > should still be handled by the old info tag, as long as two conditions > are satisfied: (a) the textual format (braces and commas) is the same > and (b) this plan can be specified back to the engine and be > successfully accepted. > > As you could recall, the plan output has already been changed twice in > the recent FB history: (1) spaces were added after commas and (2) new > ORDER X INDEX (Y) output has been introduced. I don't remember any > related complaints by the tool makers. > > So my suggestion is to agree on returning the new extension using the > old info tag and close this discussion. > > > Dmitry > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > Firebird-Devel mailing list, web interface at > https://lists.sourceforge.net/lists/listinfo/firebird-devel |