https://bugs.documentfoundation.org/show_bug.cgi?id=169424
--- Comment #4 from Robert Großkopf <[email protected]> --- I have tried with NATURAL INNER JOIN and 2 tables - won't work also with internal HSQLDB. Query GUI doesn't know all about the database, which should be queried. So It will try a construction an try to execute this construction. Database will give an error if it doesn't understand the query. When reopening a query, which didn't work with the database, GUI will test the query and decide to only open this query in SQL-mode. So the user could decide which part of the query could be used. GUI isn't able to decide this. It's the same behavior when choosing a function. If you choose a function for the query and HSQLDB doesn't know anything about this function (try INTERSECTION) you will get an error. For internal databases it would be better only to offer functions and joins between tables, which are known joins. But what to do with external databases. You will have to test first and then you see if it is working. So this description is about more than one bugy/enhancement request. 1. Joins, which doesn't work in the database, shouldn't be offered for choosing in GUI. 2. Queries, created in GUI and running in GUI (mariaDB with joins) should be opened for editing in GUI again and not only in SQL. 3. You should be able to toggle between design mode and direct SQL-mode without changing the behavior of a query. I would prefer to close this bug and open a new bug for 1. -- You are receiving this mail because: You are the assignee for the bug.
