Difference between revisions of "Database/Drivers/MySQL Native/Known Problems"
(→Specifying a different socket path is not supported (Linux)) |
(→User administration is offered in the UI, but yields an error when chosen) |
||
Line 19: | Line 19: | ||
2) Add a link from the real socket file to /tmp/mysql.sock by running this command "ln -s /<path to file>/mysql.sock /tmp/mysql.sock". However, this will probably need to be done by the root user and depending on your computer's settings the /tmp folder may be cleared each time the machine restarts. Meaning that this must be done after each boot. | 2) Add a link from the real socket file to /tmp/mysql.sock by running this command "ln -s /<path to file>/mysql.sock /tmp/mysql.sock". However, this will probably need to be done by the root user and depending on your computer's settings the /tmp folder may be cleared each time the machine restarts. Meaning that this must be done after each boot. | ||
− | === User administration is offered in the UI, but yields an error when chosen === | + | === FIXED: User administration is offered in the UI, but yields an error when chosen === |
FILL IN DESCRIPTION | FILL IN DESCRIPTION | ||
Revision as of 13:15, 6 January 2009
Contents
- 1 FIXED: Existing table fields cannot be altered
- 2 FIXED: The user interface is not remotely intuitive
- 3 FIXED: The driver doesn't run in OpenOffice.org 3.0 developer snapshots
- 4 Subforms do not work
- 5 FIXED: Specifying a different socket path is not supported (Linux)
- 6 FIXED: User administration is offered in the UI, but yields an error when chosen
- 7 Tools>Relations... not working
- 8 Installation error on x86_64 OpenOffice build
FIXED: Existing table fields cannot be altered
The implementation simply didn't get that far (css.sdbcx.XAlterTable not implemented) ... for the final release, we expect this to be fixed.
FIXED: The user interface is not remotely intuitive
That's true. The final version will run in OpenOffice.org 3.0 only, which will have a dedicated and thus vastly improved UI.
FIXED: The driver doesn't run in OpenOffice.org 3.0 developer snapshots
Well, it's not intended to do. Please use it with the 2.4 release only, everything else is not supported right now, and may lead to all kinds of unwanted results.
Subforms do not work
Well, some of them do ... more precisely, SQL statements with named parameters (":param_name") do not work in general. The ODBC/JDBC driver wrapper used to replace them with unnamed parameters ("?"), since MySQL does not understand them, but the native driver does not do this, yet. Since subforms usually make heavy use of such named parameters, they currently fail.
FIXED: Specifying a different socket path is not supported (Linux)
Currently, the driver expects the socket to be /tmp/mysql.sock
. This is hard-coded, and will be fixed with new UI (3.0). There are 2 workarounds:
1) Specify an IP number and a port number, like this: 127.0.0.1:3306/yourdb
. In this case the driver will establish a connection via TCP and not a local socket.
2) Add a link from the real socket file to /tmp/mysql.sock by running this command "ln -s /<path to file>/mysql.sock /tmp/mysql.sock". However, this will probably need to be done by the root user and depending on your computer's settings the /tmp folder may be cleared each time the machine restarts. Meaning that this must be done after each boot.
FIXED: User administration is offered in the UI, but yields an error when chosen
FILL IN DESCRIPTION
Tools>Relations... not working
Error message: Database not support relations
Installation error on x86_64 OpenOffice build
Error message:
loading component library failed: file:///home/azure/.000-2.0/user/uno_packages/cache/uno_packages/BuRBDk_/mysql-native-linux-oxt/mysqlc.so