I currently installed a MariaDB base server as local host (version: :
5.3.3-MariaDB-rc-mariadb108~oneiric-log, installed from deb repositories)
and would like to connect it with LO as a GUI (Tom would likely to
For this, I installed the MySQL connector plug-in
Connection set up: one existing database specified (this one being
completely empty) - with a user name having all rights on all databases in
Well, the connection worked fine, except that ALL existing MariaDB databases
got displayed in the table section, instead of the single one specified in
the connection set up; corresponding tables are listed below each db name.
I suppose that this was not the expected result ans I'm doubtful about
accessing simultaneously to all tables within all db.
Then the question is: what did I wrongly? How could I correct this, please?
I didn't go any further, for instance I did not test with a user having
access right only defined for the target db.
Thanks in advance for any hint or highlight!
(LO version in the signature)
Dualboot Ubuntu 11.10 amd64 - W7
LibreOffice 3.4.4 OOO340m1 (Build:402)
View this message in context:
Sent from the Users mailing list archive at Nabble.com.
For unsubscribe instructions e-mail to: firstname.lastname@example.org
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
- [libreoffice-users] MySQL native connector - several databases retrieved? · fmayo
Impressum (Legal Info)
: 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