On Tue, 2019-07-23 at 18:08 +0200, Robert Großkopf wrote:
Hi Harvey,
I am not using macros (yet...hmm). I create the queries with the
GUI in
SQL view.
I execute using the 'Run Query (F5)' function from the editor. The
SQL
text is not allowed to be stored with the syntax error in the one
case.
In the case of the shorter command, the SQL text is stored as a
query
and, it seems, could be run from the GUI, if it weren't for the
executeUpdate() error.
The query-editor will only work with queries, not with updates or
inserts. You have to start the command through
Tools > SQL
in the Base-file.
The database itself is backend mariadb connectect via JDBC.
So you have to use
UPDATE `Adressensammlung`.`Adressen` SET `Adressen`.`Print_flag` =
TRUE
WHERE `Adressen`.`Xmas` = TRUE;
Regards
Robert
--
Hi Robert,
Thanks a lot, that works fine!
A bit disappointing though. Is there no possibility for storing those
kinds of SQL statements, so that they could be used again?
I have a few in mind, and it seems a bit primitive to have to create a
clipboard type of text file for that kind of thing.
Cheers
Harvey
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.