[ANNOUNCEMENT] MySQL-Connector Extension

users
#1

I have uploaded two connectors to the Extension website under Base Extensions version 1.0.3. Both are for Linux only. One is 32 bit (x86) and the second is 64 bit (x86_64). For now, either should be downloaded for testing only. The 32 bit connector works on LO 4.0.x and 4.1.0 alpha for both Ubuntu 12.04 and 12.10. I need others to test these on a variety of Linux distributions before I can have a final version available here.
      If you test one of these, please send an email to me with the results.

--Dan

#2

Hello Dan,
Sorry to be a nuissance - but I can only find Access2Base under Base Extensions.
The page is
http://extensions.libreoffice.org/extension-center?getCategories=Base_Extension&getCompatibility=any
Is this correct?
Regards
Heinz

#3

When I went to the Extension web page, I had to select "Base Extensions" and "Any Version". That is when I saw two extensions listed: "Access2Base" and "MySQL Native Connector". When I clicked on the latter, I went to the MySQL Native Connector page. Next you need to click the "1.0" link below Version to get to the download page.
      A direct link to the downloads:
http://extensions.libreoffice.org/extension-center/mysql-native-connector/releases/1.0.

--Dan

#4

Thanks, Dan. I have downloaded the connector and will install it on my
32-bit-Linux-Debian and Debian-Wheezy systems.
Regards
Heinz

#5

Hi Dan,
Thanks again! Eureka! I had to add the ".oxt" file extension to the name.
Now I can access a MySQL database stored on the Debian Wheezy system (MySQL 5.5)
through a LAN. They are both 32-bit.
I will test it more in the coming days and report on the results to you.
I wonder about ONE thing: Even though I specify the name of the database for
the connector, LO-Base displays ALL the additional databases that are defined
on the server. This is unlike JDBC/ODBC where only the ONE DB mentioned in the
definition of the LO-odb-file is shown in the list. Of course one can always
specify MySQL-GRANT-statements as required. But somehow I would prefer to only
see the intended DB.

Kind regards,
Heinz

#6

Hi again,
Your connector also works from the client an Linux-Mint-Nadia to a server
running Debian-Squeeze and MySQL 5.1. Super!!
And - by the way -
LO is at Version 4.0.1.2 (Build ID: 84102822e3d61eb989ddd325abf1ac077904985)
Regards
H

#7

So, you also noticed this. When using the native connector, MySQL will display all of the databases for which the given user has been given access. JDBC/ODBC will only display the specific database that is listed in the database file.
       Some thoughts. If you are going to use the native connector for MySQL, group the type of databases contained in it according to use. Then allow one or a few users access to each group.
      With JDBC/ODBC, you have to have a Base file for each database. Or, you can right click in the list section of the database window to select Database > Properties. There you can change the database you want to view.
       To view only one database at a time using the native connector, you would have to set the permissions so that only one user can access a given database other than the administrator. Then you can have base connected to MySQL and change the user name doing what I mentioned in the previous paragraph.
       Maybe you have a different method of switching databases when you need to do so.

--Dan

#8

Hi Dan,
Thanks for the hints. So far I am the only user, but shortly this will not
be the case anymore. Non-Administrator users will only need access to ONE
DB anyway. So I won't grant them access to any of the others. Also, I will
restrict access to the tables and views within that DB to the users that
need to work with them.
Regards
Heinz

#9

Hi Heinrich,

I wonder about ONE thing: Even though I specify the name of the database
for
the connector, LO-Base displays ALL the additional databases that are
defined
on the server. This is unlike JDBC/ODBC where only the ONE DB mentioned

This is a defect of the mysql driver code as far as I remember. I don't
remember now whether turning off/on the "Ignore Driver Privileges" in
the Adavanced tab of the database connection properties helps or not. I
have a vague recollection that activating that option is supposed to
make the default behaviour fall back to the mysql user table/column
privileges.

Alex

#10

Hi Alex,
Thanks for your hint! I had "Ignore Driver Privileges" checked BEFORE! Turning
it off didn't make any difference...
Regards
H

#11

Hi Heinrich,

Thanks for your hint! I had "Ignore Driver Privileges" checked BEFORE!
Turning
it off didn't make any difference...

Well at least that's another thing to report as not working :wink:

Alex