Title says it all really. I've found that occasionally I want to run a query which either deletes or updates records according to certain criteria. Typing the SQL is always possible but is error-prone. A graphical (and storable) way is greatly preferable. This has been available in Access for ages (I last used that program in about 2000); surely it's time that LO had this feature?
*** This bug has been marked as a duplicate of bug 31398 ***
I don't think it's the same. I'm asking for a graphical way of inputting update/delete queries. RFE 31398 is asking for LO to allow such queries to be input in SQL and use the HSQLDB permissions for access control (as I read it).
> I don't think it's the same. I'm asking for a graphical way of inputting > update/delete queries. RFE 31398 is asking for LO to allow such queries to > be input in SQL and use the HSQLDB permissions for access control (as I read > it). Bug 31398 is about a possibility to save SQL-Code for update/insert/drop. The title of the bug is misleading: sql-editor is used in bug 31398 for both: The GUI for queries and the possibility to put code to tools > SQL. Look at this, copied from the original report: --------- when run as query fails: UPDATE "Table1" set "Table1"."fld-flag" = False where "Table1"."fld-flag" = True; (error was: "LibraOffice Base: The data content could not be loaded. Statement does not generate a result set.") when run same sql code as tools-sql-execute_command it succeeds ("Command successfully executed."): UPDATE "Table1" set "Table1"."fld-flag" = False where "Table1"."fld-flag" = True; --------- So I think this is a duplicate.
Robert, I disagree. Your clips from the bug 31398 are both for SQL that's been typed in. I'm asking for a graphical way of generating the query. I've changed the title to make it clearer.
*** This bug has been marked as a duplicate of bug 37599 ***