LO-Base - Autoreconnect

users
#1

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

#2

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

#3

Hi :slight_smile:
If you haven't already done so then posting this idea as a "feature
request" would be a really good way forwards. Unfortunately not many devs
dare take on the challenge of working with Base. So the next step might be
to promote it somewhere, preferably in a few different places. This
mailing list is a good one. Perhaps a MySql forum too. Perhaps some sort
of crowd-funding or crowd sourcing place. So, i think you are already
doing the right sorts of things.

Wrt trying to access a remote server, perhaps using ssh from a linux
command-line might be a way in? Dealing with the server's sys.admin might
be a blocker, or rather finding a way of contacting them might be.
Regards from
Tom :slight_smile:

#4

Hi :slight_smile:
That might be another neat work-around, perhaps as a 'temporary' system
while waiting for more devs to join in with working on Base.
Regards from
Tom :slight_smile:

#5

Hello,
Thanks for the quick replies. Some points...
Disconnecting/Reconnecting the MySQL server from LO-DB is not really a
work-around. Essentially confirming the displayed message mentioned (i.e.
"The last package sent to the server...") with just one click is in my
opinion more efficient, although not really good enough for somebody not
quite as "benevolent" as myself wrt doing "serious" day to day work with LO-BASE.
Regarding SSH to the server: I use the MySQL client all the time without problems
I am not allowed to use either by the sysadmin at the server. However, while the
MySQL client is o.k. for DB-Admins to do maintenance work (like backups), it is
not fit for everyday production type transaction-type work. By the way - the same
applies also to tools like phpMyAdmin or MySQL workbench.
I will look into this as a feature request...
Regards from Salzburg (hardly any snow here - in January! Where is the world
getting to, I wonder!

#6

It is already reported as a feature request :

https://bugs.documentfoundation.org/show_bug.cgi?id=88796

for which you are the bug reporter... :wink:

Alex

#7

Thanks Alex,
Of course, I am getting more modest these days! I can accept the "behaviour" under
JDBC. I would only like to NOT have to press the "ok" button to confirm the message
every time the MySQL server times out. Especially since in my connection string for
the db I anyway specify that I want to reconnect automatically. I will add this to
the bug report/feature request.
Greetings from Salzburg
Heinz