Difference between revisions of "Database/Drivers/MySQL Native"
Stefanhinz (Talk | contribs) (→Known issues) |
|||
| Line 2: | Line 2: | ||
== Known issues == | == Known issues == | ||
| − | + | === Existing table fields cannot be altered === | |
| − | + | The implementation simply didn't get that far ... 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 OpenOffice.org 3.0 only, which will have a dedicated and thus vastly improved UI. | |
| − | + | === 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. | ||
| + | === Specifying a different socket path is not supported (Linux) === | ||
| + | Currently, the driver expects the socket to be <code>/tmp/mysql.sock</code>. 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: <code>127.0.0.1:3306/yourdb</code>. In this case the driver will establish a connection via TCP. | ||
| + | === User administration is offered in the UI, but yields an error when chosen === | ||
| + | FILL IN DESCRIPTION | ||
| + | |||
[[Category:Database|MySQL]] | [[Category:Database|MySQL]] | ||
[[Category:Database Drivers|MySQL]] | [[Category:Database Drivers|MySQL]] | ||
Revision as of 14:17, 23 April 2008
This page is dedicated to the MySQL native driver, which is currently being developed by MySQL and OpenOffice.org engineers.
Contents
- 1 Known issues
- 1.1 Existing table fields cannot be altered
- 1.2 The user interface is not remotely intuitive
- 1.3 The driver doesn't run in OpenOffice.org 3.0 developer snapshots
- 1.4 Subforms do not work
- 1.5 Specifying a different socket path is not supported (Linux)
- 1.6 User administration is offered in the UI, but yields an error when chosen
Known issues
Existing table fields cannot be altered
The implementation simply didn't get that far ... 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 OpenOffice.org 3.0 only, which will have a dedicated and thus vastly improved UI.
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.
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: 127.0.0.1:3306/yourdb. In this case the driver will establish a connection via TCP.
User administration is offered in the UI, but yields an error when chosen
FILL IN DESCRIPTION
