On Thu, 2017-11-30 at 15:50 +0100, Robert Großkopf wrote:
...
It has never beeen intended that the query-editor is used for
changing
data. There is a feature-request for this:
https://bugs.documentfoundation.org/show_bug.cgi?id=31398
since 7 years.
The risky feature is: the native connector of MySQL will allow this
at
this moment.
If we write a bug-description about this the solution at this moment
could be the "feature" of the direct connection will be taken away
instead of changing something in the GUI, which works right with
internal Database and other external connectors.
Obviously, I found this behaviour (by accident) because I was looking
for it, and because I needed it. Also obviously, my feeling is that
LOBase is not doing itself a favour by restricting usage of SQL in this
way. I would prefer a feature that allowed data manipulation via
queries, but caught risky situations with a warning, for example.
Or is there another simple way of data manipulation in LOBase, that
would not be easier by resorting to phpMyadmin or Mysql Workbench?
Regards
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/
All messages sent to this list will be publicly archived and cannot be deleted
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.