Version: 2.4 alpha3 (Calligra 2.4 alpha3) (using KDE 4.6.0) OS: Linux The query designer seems to lack quite a few features, SQL supports some but changing from one view to the other provides inconsistent data to one or the other view (eg LIKE, etc). That is a SELECT statement in SQL view is overwriten by the one on Design view. The data displayed on the Data view are also inconsistent. Updating both Designer and SQL sometimes results the query displaying results from the statement in Design and other times from the statement in SQL. As a workaround, until both views (Design, SQL) are consistent with the SELECT features they provide, the user should be allowed to work in ONLY ONE of the two query design modes. Reproducible: Sometimes Steps to Reproduce: Open query at design > add a table and columns Switch to SQL view > edit sql SELECT statement Switch to Data view Switch back to design view, then SQL view Actual Results: Changes to designer are not always reflected in SQL and vice versa. Expected Results: Editing Query Design or SQL, the select statement should be updated on both views. Other examples are: 1) In a WHERE field = value clause criteria column displayes just the value, however when using WHERE field LIKE value, LIKE is displayed as well (maybe include = in the criteria column? Other operators are displayed). 2) Other SQL predicates are not supported altogether (eg IN, BETWEEN, etc) 3) Bug 277869. https://bugs.kde.org/show_bug.cgi?id=277869
The workaround makes sense but it is not clear if it's good usability-wise.
I agree it is not the best solution, still the easiest and most bullet-proof until we can provide consistent features betweeen Design & SQL
Splitted out a 'wish' part of this big to #289293
Ah mistake, sorry, ignore comment #3.
Regarding "1) In a WHERE field = value clause criteria column displayes just the value, however when using WHERE field LIKE value, LIKE is displayed as well (maybe include = in the criteria column? Other operators are displayed)." Operator '=' is the default in the criteria column. So skipping the '=' operator in value 'foo' is equivalent of value ='foo'.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.