Apache OpenOffice (AOO) Bugzilla – Issue 16273
MySQL tables created in unwanted database
Last modified: 2006-05-31 14:29:06 UTC
* have a MySQL server hosting at least two databases * Have a MySQL ODBC driver greater or equal 3.51, so it supports catalogs (as database names) * in OOo, create a MySQL/ODBC data source for the _alphabetically_second_ of the databases on this server * open a new table design for this data source * insert some arbitary fields * save the table => in the dialog where the name is to be entered, there is also a selection box for the catalog in which the table should be created. This lists contains the databases. By default, the alphabetically first database/catalog is selected (note that this is not the one which the data source works with). * press OK => the table is created, but in the wrong database. If you want to display it in the data source browser (where it appears), then nothing happens - not even an error message. This is bad, as unexperienced users won't know what the catalog is for, and thus leave it untouched.
targeting. I consider this 1.1.1 worth, because for n-1 databases on a MySQL server (with n database at all), the creation of tables will yield unwanted results. FS->OJ: please also have a look why selection the table in the DSB fails silently - normally there should be an error message.
Fixed in cws dba01pp1.
verifiy in dba01pp1
.
change subcomponent to 'none'