Difference between revisions of "Database/Drivers/MySQL Native/Known Driver Problems"
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! | '''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! | ||
+ | |||
= Connector/OpenOffice.org development issues to discuss with OOo team = | = Connector/OpenOffice.org development issues to discuss with OOo team = | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== MySQL related == | == MySQL related == |
Revision as of 08:26, 8 January 2009
Attention: This page is currently being migrated to a page called Known Problems, so for the moment, please don't add anything new here!
Contents
- 1 Connector/OpenOffice.org development issues to discuss with OOo team
Connector/OpenOffice.org development issues to discuss with OOo team
INSERT does not work
Inserting data into a simple table does not work. Works fine when using the JDBC driver.
CREATE TABLE `source` ( `id` int(11) NOT NULL, `col1` int(11) NOT NULL, PRIMARY KEY (`id`), KEY `idx_col1` (`col1`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1
information_schema (I_S) not shown in schema list
SHOW DATABASES shows the I_S. When quering the I_S for schema, the I_S will not expose itself. Different versions of Connector/C++ use different ways to fetch schema lists. Until and including Alpha SHOW DATABSES is used.
When using the JDBC driver and specifying no database in the connection URL no schemata are shown at all.
TINYINT / BOOLEAN
Educate Base users on MySQL Server type mappings, for example BOOL[EAN] -> TINYINT.
DatabseMetaData::getColumns() COLUMN_SIZE
DatabseMetaData::getColumns() takes COLUMN_SIZE from getDisplaySize(). getDisplaySize() returns always 20, which needs to be tweaked on a per-datatype basis.
Affected: DECIMAL/FLOAT.
DatabseMetaData::getColumns() DECIMAL_DIGITS
DatabseMetaData::getColumns() does not set DECIMAL_DIGITS. Therefore, Base does not show it properly.
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.