On Wed, 2019-07-17 at 09:09 +0200, Robert Großkopf wrote:
Hi Harvey,
couldn't see this behaviour in LO 6.2.5.2 on OpenSUSE 15, 64bit rpm
Linux. But my MariaDB is a local database. Think it is a problem of
the
remote-connection to your database. The changing of the table must
reach
the database and after changing the table inside the database the
information could be send back to the query.
Do you use parameters for the connetion to the database, for example
jdbc:mysql://«Host of
database»:3306/«databasename»?autoReconnect=true
@Dan: If you add a field to a table for an external database the
Base-file must not be saved. There has nothing been changed in Base,
only in the (external) database.
Regards
Robert
--
Homepage: http://robert.familiegrosskopf.de
LibreOffice Community: http://robert.familiegrosskopf.de/map_3
Hallo Robert,
it seems that autoReconnect=true does the trick. I had been using the
MySQL(JDBC) method where there seemed to be no place to set the
autoReconnect option. Having switched to the pure JDBC method, I can
add autoReconnect=true and it works now as expected.
Many thanks!
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.