Difference between revisions of "Database/Drivers/MySQL Native"
From Apache OpenOffice Wiki
| Line 5: | Line 5: | ||
* '''The user interface is not remotely intuitive'''<br/>That's true. The final version will run in OpenOffice.org 3.0 only, which will have a dedicated UI. | * '''The user interface is not remotely intuitive'''<br/>That's true. The final version will run in OpenOffice.org 3.0 only, which will have a dedicated UI. | ||
* '''The driver doesn't run in OpenOffice.org 3.0 developer snapshots'''<br/>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 kind of unwanted results. | * '''The driver doesn't run in OpenOffice.org 3.0 developer snapshots'''<br/>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 kind of unwanted results. | ||
| + | * '''sub forms do not work'''<br/>Well, not all of them don't ... more precise, in general SQL statements with named parameters (":param_name") do not work. 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 sub forms usually make heavy use of such named parameters, they currently fail. | ||
[[Category:Database|MySQL]] | [[Category:Database|MySQL]] | ||
[[Category:Database Drivers|MySQL]] | [[Category:Database Drivers|MySQL]] | ||
Revision as of 18:29, 17 April 2008
This page is dedicated to the MySQL native driver, which is currently being developed by MySQL and OpenOffice.org engineers.
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 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 kind of unwanted results. - sub forms do not work
Well, not all of them don't ... more precise, in general SQL statements with named parameters (":param_name") do not work. 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 sub forms usually make heavy use of such named parameters, they currently fail.
