| Summary: | : MySQL Database Connection Failure with Base | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | jive.email |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | CLOSED WORKSFORME | ||
| Severity: | normal | CC: | iplaw67 |
| Priority: | medium | ||
| Version: | 3.3.0 release | ||
| Hardware: | x86 (IA32) | ||
| OS: | macOS (All) | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
|
Description
jive.email
2012-04-18 09:21:39 UTC
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. Alex Can confirm that socket field not present in Mysql connection wizard dialog WITH mysql JDBC connector on LO master build : Version 3.7.0.0.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. Alex 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. Alex No news from original submitter since first post on 18/04/2012. Closing as WFM. |