|
|
| (3 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | '''Attention''': This page is currently being migrated to a page called [[Database/Drivers/MySQL Native/Known Problems|Known Problems]], so for the moment, please don't add anything new here!
| + | #REDIRECT [[Database/Drivers/MySQL Native/Known Problems]] |
| − | | + | |
| − | = Connector/OpenOffice.org development issues to discuss with OOo team =
| + | |
| − | | + | |
| − | == Unclassified and first preview version related issues ==
| + | |
| − | | + | |
| − | === 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.
| + | |
| − | | + | |
| − | === Tools -> User Administration... User administration is offered in the UI, but yields an error when chosen ===
| + | |
| − | | + | |
| − | '''Same restriction applies for MySQL JDBC driver -> won't fix?'''
| + | |
| − | | + | |
| − | === Tools -> Relations... not working ===
| + | |
| − | | + | |
| − | Error message: Database not support relations. '''Same restriction applied to JDBC driver -> won't fix?'''
| + | |
| − | | + | |
| − | === FIXED issues ===
| + | |
| − | | + | |
| − | ==== 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.
| + | |
| − | | + | |
| − | ==== 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.
| + | |
