Hello Heinrich,
I never used Base, though for other projects I use MySQL and other db's.
As a workaround, I wonder whether it is possible to disconnect the
database from within LO after each query? Then, you should be able to
reconnect when a new query is requested. This also has the advantage
you won't have many simultaneous connections on the db.
Met vriendelijke groeten, Salutations distinguées, Kind Regards,
DRIES FEYS
CORPORATE SERVICES • Specialist Software Developer
TVH GROUP NV
Brabantstraat 15 • BE-8790 WAREGEM
T +32 56 43 42 11 • F +32 56 43 44 88 • www.tvh.com
Watch our company movies on www.tvh.tv
Business Innovation
through
Information Technology
bi2t.tvh.com
On 27 January 2016 at 11:29, Heinrich Stoellinger <hc.stoellinger@aon.at> wrote:
Hello,
I have been an avid user of LO/OO-Base for years, using it to connect to a
MySQL database for everyday work --- couldn't do without it. I am convinced
that a good connection to a DB-backend like MySQL/MariaDB is essential for
LO to be successful in a "real" business environment.
As I have mentioned in earlier messages to the list, I use JDBC to connect
to my remote DB-server as well as the native MySQL-connector for my local
test server.
Unfortunately I don't have access to the remote server and therefore cannot
change its idle-timeout, which is set at 60 seconds.
On my Linux-Mint system I also connect to the server via the command line
MySQL client. If - after going away for more than 60 seconds - I come back
to do more work, the client reports the timeout, but reconnects
automatically.
This is kind of acceptable, even in a business production environment.
Unfortunately the native connector does not support "autoreconnect". This
means that one would have to restart LO in case of a timeout (unacceptable
for "serious" work!) On the other hand, JDBC does allow the specification of
"autoreconnect=true" as part of a connect string. However, unlike in the
case
of the MySQL command-line client, LO-Base doesn't simply reconnect
AUTOMATICALLY,
but displays a message such as "The last package sent to the server was x
seconds ago, the lase received packed was y seconds ago".
This means that whenever a timeout occurs, one has to confirm the wish to
reconnect - even though one has specified that one wants to do this in the
connect string when defining the DB-connection properties in the first
place!
I wonder how difficult it would be to implement such a REALLY automatic
reconnection...
Regards (and I appologise for the lengthy description...)
H. Stoellinger
--
Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems?
http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be
deleted
--
**** DISCLAIMER ****
http://www.tvh.com/glob/en/email-disclaimer
"This message is delivered to all addressees subject to the conditions
set forth in the attached disclaimer, which is an integral part of this
message."
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://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.