Submitted as OpenOffice Bug 119242.
A similar problem occurs with LibreOffice.
Can't seem to connect to a MySQL database in Base (in OS X Lion.)
The "Database properties - Additional Settings" dialog "Socket" field is a bare
text box that is missing a filesystem browser button to select a socket file,
i.e. "/usr/local/zend/mysql/tmp/mysql_sock". This field is not even available using the initial database connection wizard pages; I went in and found it after trying to create a connection using a MYSQL (JDBC) connection with File / New / Database and having it fail (after a long time looking at the spinning beach ball), then going in to the connection properties after Base loaded and choosing MySQL (Native) from Edit / Database / Connection Type.
Then, the "Finish" button never became available.
I was able to get the "Finish" button to become active a second time through Edit / Database / Connection Type (don't see why...), but then in trying to select Tables on the left in Base, got a dialog with the following error:
"The connection to the data source "xxxxxxxxx" could not be established. The connection to the external data source could not be established. No SDBC driver was found for the given URL."
This error also occurs when trying to connection via the port vs. the socket.
I am able to make this connection via a mysql prompt in Terminal, and through phpMyAdmin - tested at the same time / after the OpenOffice connection error.
Steps to reproduce:
1. File / New / Database - no MySQL (Native) option
2. Edit / Database / Connection Type = MySQL (Native) - no Finish button
3. Edit / Database / Connection Type = MySQL (Native) - click Finish button
4. Click Tables on left - observe error dialog per above.
Eventual failure with SDBC driver error.
Be offered the option to select a socket file, and create a database
Platform (if different from the browser):
Mac OS X Lion 10.7.3 (11D50d)
The version text in the OpenOffice / About menu is not selectable to be copied,
but it says:
OOO330m20 (Build: 9567)
Safari Version 5.2 (7535.18.5)
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_3) AppleWebKit/535.18.5
(KHTML, like Gecko) Version/5.2 Safari/535.18.5
I tried to search for existing bugs, but couldn't see a way to on the web page
I was offered.
Also, the Browse button on the bug submission page doesn't work - it may be
Ghostery in Safari on OS X Lion.
I will look at this and try to confirm.
However, I can already state that with a build from master of today I can open an existing configured ODB file that uses the mysql native connector (which I built myself). LO dev then crashes and dies, but I'll check other reports for that.
Can confirm that socket field not present in Mysql connection wizard dialog WITH mysql JDBC connector on LO master build :
Version 188.8.131.52.alpha0+ (Build ID: 042686d) from yesterday
In LO 3.3.4, on Windows, with the native mysql connector extension, a dialog field is provided to enter the socket to the running mysql process (if necessary).
However, I CAN set up and use a mysql JDBC connector-based ODB on Mac OSX Lion 10.7.4, using mysql-connector-jdbc-5.1.18
So this works for me.
I'm having difficulty what exactly you consider to be buggy :
- the fact that the wizard for the JDBC connector connection setup has no field in which to enter the socket information ; or
- the fact that you want to be able to browse to the location of the socket.
In the second case, a normal user wouldn't be able to see the contents of /tmp/mysql.sock using the system navigation dialogs, because these are hidden from the user on OSX (well SnowLeopard and Lion, at least), as would be /usr/local/...this is a limitation imposed by the OS.
I do agree however, that the user should be able to enter the path destination of the mysql.sock in the in wizard dialog, as is the case with native mysql connector extension (on Windows with LO 3.3.4, at least, I haven't checked elsewhere).
So, IMHO, both points seem to relate more to an RFE (request for enhancement), rather than a bug, as such, since as you mentioned, you seem to be able to enter the sock data post-wizard setup, which is a workaround.
You mention OpenOffice 3.3.0, this is the LibreOffice bug tracker.
Which version of LO are you using ?
If you are using 3.3.0 of LibreOffice, you should upgrade, that version was pretty unstable when it came to database business.
Am not confirming, requesting more info.
I will close this as worksforme, if I don't hear back from the original submitter.
No news from original submitter since first post on 18/04/2012. Closing as WFM.