Database/Drivers/MySQL Native/Known Problems

From Apache OpenOffice Wiki
< Database‎ | Drivers‎ | MySQL Native
Revision as of 06:10, 30 April 2008 by Frank Schoenheit (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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.

The user interface is not remotely intuitive

That's true. The final version will run in 3.0 only, which will have a dedicated and thus vastly improved UI.

The driver doesn't run in 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.

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). As a workaround you should specify an IP number and a port number, like this: In this case the driver will establish a connection via TCP.

User administration is offered in the UI, but yields an error when chosen


Personal tools