[kepler-dev] [Bug 2143] - fix functionality and GUI issues with query builder

bugzilla-daemon@ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Tue Nov 1 14:35:21 PST 2005


http://bugzilla.ecoinformatics.org/show_bug.cgi?id=2143





------- Additional Comments From jones at nceas.ucsb.edu  2005-11-01 14:35 -------
Issues submitted by Efrat Frank regarding Query Builder in Kepler.
--------------------

1. No conversion available from sql to xml query representation, thus 
changes made through the sql tab don't get reflected. Perhaps the xml 
representation is redundant here..

2. Sometimes updates don't get reflected the first time around, but only 
after reopenning the query builder and re-updating.
    E.g. when changing the intermediate tab:
    The first time creates the following xml representation:
       (*) <query advanced="false">
            </query>
    Only the second time, the updates get reflected, given that the 
current sqlDef attribute value is (*)). Perhaps (*) should be set as the 
default initial sqlDef.

3. Confusions between changes made through various tabs.
    Usually only the last used tab's changes get reflected.
    Sometimes when changing the standard tab along with other tabs, only 
the standard tab changes get reflected (this seems to be related to 
problem 2, and could probably be solved using (*) as the default 
expression).
    Going between advanced tabs to the standard tab, causes several 
representation exceptions (understandable, as some parts cannot be 
evaluated in the standard tab - should not allow going backword between 
the tabs once the more advanced tab is updated).
    On the other hand, there may also be conflicts between the tabs (the 
intermediate and advance), so one of them needs to be eliminated.

4. When traversing between tabs to the SQL tab, the query in the SQL 
doesn't reflect the user current modifications, the changes are 
reflected only after commiting.

5. Sometimes after several modifications (in the advanced and 
intermediate tabs) the query builder no longer loads. It seems to be 
related to exception when parsing the xml query representation.

6. The operator criterion in the standard tab doesn't get reflected in 
the xml representation.


More information about the Kepler-dev mailing list