We’ve got a common .odb file used by everyone who accesses our MySQL backend. The file is stored on our central server. The advantage of this approach is that changes only have to be made one place to the interface. What I don’t like about it is that, because it’s all one .odb file, it always suggests the login of the last user to log in. Is there a way to prevent this?
Is it really the last user? Or is the file opened and LO of other user running while you connect to the file?
User-name could be deleted in Edit → Database → Properties → User-Authentication.
It’s definitely not being accessed from multiple machines simultaneously. I really do think it is the most recent MySQL account to access the database. Honestly, I would prefer that it not suggest any username to this behavior.
You are asked for a username when opening and this is always the same user name? Deleting of user-name in properties of the database has no effect?
No, deleting the user name in properties has no effect. I even saved the .odb file after the deletion, and then set the .odb file to Read-only, and it’s still retaining the last user name used. This is LO 5.3.6.1.
Is it possible this behavior is built into the MySQL Connector?
I have tested it here with only one user. The direct connection works here like expected. When deleting the username I am asked for a username an a password. When closing only the Base file and reopening it the connection still exists. When closing whole LO the connection will be deleted. Open the Base file next time I am asked for username and password.
Is there any other way of connection like connecting by macro?
You are using really LO 5.3.6.1? For this version no direct connection has been bundled with LO. The first version, which had included the extension, which exists before, is LO 6.2.
I’m using the MySQL-connector-java-5.1.44-bin.jar from Oracle to connect. I set it up through Options>Advanced>Class Path…
Are you saying I could avoid having to use the community connector by simply upgrading to the latest stable release of LO?
I have now tested the connection with JDBC. Works the same way. Deleting of the user name doesn’t show the user any more. I have to input the user every time I connect to the database.
With JDBC it is possible to set the connecting user in the connection-string of JDBC. Did you connect to MySQL through MySQL → JDBC or through JDBC directly, where the connection-string could be edited.
Difference between our installations might be: I’m using OpenSuSE and MariaDB.
I wouldn’t change between the direct connection and JDBC, if all is running well with JDBC except the user name. There are different bugs in every connection you choose.
This is the reason why I distribute one backend file to each user. Over time your database design will be finished and changes will become rare.