Hi, i answer with delay - in Poland November 11 is the national holiday of Independence >>then i would not use underscores inside the tags and params. yes - you have right here >>Also i would prefer using the base operation as tag and not everything >>encapsulated inside <Node operation=".... this is not good - think about parser which display graphical plan. It should know that some node is operation node not some property node and it can show graphical representation without knowing all kind of operation at start. Look at xml plan representation in MSSQL - i tried to follow this plan format regards, Karol Bieniaszewski W dniu 2015-11-11 02:05:33 użytkownik Arno Brinkman <[email protected]> napisał: Hi, Just my 2 cents: I can see the benefit of an XML output, but then i would not use underscores inside the tags and params. Also i would prefer using the base operation as tag and not everything capsulated inside <Node operation="...."> Something like: <SelectExpression> <Filter> <NestedLoopOuterJoin> <NestedLoopInnerJoin> <Filter> <Table alias="R">RDB$RELATIONS</Table> <FullScan/> </Filter> <Filter> <Table alias="RF">RDB$RELATION_FIELDS</Table> <BitMap> <Index Scan="Range" Matching="Full">RDB$INDEX_4</Index> </BitMap> .......... </Filter> </NestedLoopInnerJoin> </NestedLoopOuterJoin> </Filter> </SelectExpression> Kind Regards, Arno Brinkman ABVisie
------------------------------------------------------------------------------
Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
