[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[libreoffice-users] Re: Connecting to a MySQL database with native password using LO 6.4.6.1



On 7/29/20 10:41, Dan Lewis wrote:
I am having problems connecting directly to the MySQL server (8.0.21) with this version of LibreOffice. I had no problems before upgrading to version 6.4.6.1. There is no problem while using the Mac OS nor when using the connector for MariaDB. I am wondering if someone using the Windows OS has a problem.

I can make a connection if I use the MySQL J connector (8.0.21)using my native password. Under this same set up, I can also connect using another user which uses the SHA2 password. Both of these are using LibreOffice 6.4.6.1.
I also have version 7.0.0.2 (7.0RC2) installed. The direct connector will not allow me to access MySQL, but the MySQL J connect allows access with the same password.

System: Ubuntu 18.04 LTS 64 bit, MySQL components are all the latest (8.0.21) updated the middle of June. The LIbreOffice version is a prereleased version which had been downloaded and installed last Thursday.

Dan


--
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

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.