Difference between revisions of "Database/Drivers/MySQL Native/Known Problems"
(→No way to set MySQL specific table attributes) |
(→Empty schemata not shown) |
||
Line 2: | Line 2: | ||
− | == Empty schemata not shown == | + | === Empty schemata not shown === |
Create an empty schemata/database. Create a new Base database which connects to an empty MySQL database. The MySQL database is not shown. | Create an empty schemata/database. Create a new Base database which connects to an empty MySQL database. The MySQL database is not shown. |
Revision as of 08:12, 8 January 2009
This page lists the currently known problems with the MySQL Native Driver, aka MySQL Connector/OOo.
Contents
Empty schemata not shown
Create an empty schemata/database. Create a new Base database which connects to an empty MySQL database. The MySQL database is not shown.
Severity: desired
Reason: OOo calls getTables() - no tables - schema not displayed. Setting might even be cached - verify that database becomes visible after creating table (from mysql prompt) in schema.
DECIMAL shown as TEXT
Base shows numerical DECIMAL columns as TEXT (in the table design?).
Severity: required
I'm 95% sure C/C++ and C/OOo report a proper column type.
Create a new Base database that connects to a MySQL schemata "test". Have "test" in the connection settings! OOo will ignore it and query MySQL for all tables in all schematas, and also display all those tables.
As a consequence the user will see all schemata he has access to not only the schemata/database "test" as requested in the connection settings
Severity: desired
No default schema on table creation
Base does not preselect a default schema in the table editor dialog. Its does not even if you connect to a certain schema by specifying it in the connection settings.
Severity: desired
No way to set MySQL specific table attributes
The Base table editor does not give access to table attributes. Not even basic ones such as the Engine (MyISAM: non-transactional, InnoDB: transactional).
Severity: 1.1
Base does not recognize schema changes
After connecting to a database and opening a table once, Base will not recognize changes applied to the DB schema meanwhile when opening the table in the table editor again.
Severity: undecided
Is this really an issue? There's View/Refresh Tables
, if needed.
Base table column comments
Base table column comments are not synchronized with the MySQL DB and its schema. Existing comments are not displayed in Base, and entering comments in the table editor is not propagated to MySQL.
Severity: later
That's a known issue with all database types. The column description as displayed in Base is purely client-side, and stored within the .odb file only. There's also an issue for this, but I'm too lazy too search for it right now ...