Apache OpenOffice (AOO) Bugzilla – Issue 95792
MySQL ODBC editing tables broken
Last modified: 2023-03-18 19:49:44 UTC
Hi, first some information: Mini-Mac : 1,42Ghz PPC G4 - 1 GB DDR-SDRAM, Mac OS X 10.4.11 OpenOffice Version 3.0 - 300m9 (Build: 9358) MySQL-ODBC-Driver: MySQL Connector/ODBC 5.1.5 [ODBC Data Sources] myodbc = MySQL ODBC 5.1 Driver /Library/ODBC/odbc.ini: [ODBC] Trace = 0 TraceAutoStop = 0 TraceFile = TraceLibrary = [myodbc] Driver = /usr/local/lib/libmyodbc5.so DATABASE = example DESCRIPTION = Some Description here OPTION = 3 ReadOnly = No PWD = HIDDEN-HERE PORT = 3306 SERVER = 192.168.178.200 UID = HIDDEN-HERE /Library/ODBC/odbcinst.ini [ODBC Drivers] MySQL ODBC 5.1 Driver = Installed [ODBC Connection Pooling] PerfMon = 0 Retry Wait = [MySQL ODBC 5.1 Driver] Driver = /usr/local/lib/libmyodbc5.so SETUP = /usr/local/lib/libmyodbc3S.so -------------------- Description: I have created a mysql database on an Ubuntu Linux server (Hardy release). I created a new database document in OpenOffice under MAC OS X. I first selected the mysql-driver, then the odbc option. Anything else defaults. I chose the tables tab and created a new table called Tabelle1 (Default name in german). I added some fileds: name, given name and street as well as an ID, primary key with auto increment. All with OOo. I saved the table. Checking on the mysql-server side, the table got created successfully. After that I saw the newly created table in OOo and double clicked it for editing. The cursor was blinking, but as I started typing, nothing happened. I went to the server side and inserted some data with the defined database user (To make sure that it was not a privilege problem). After that I checked again under OOo. The data sets were listed now. I selected one line under OOo and told to delete this set and this worked! So I can read and delete data under OOo, but can not insert anything. I copied over the odbc-stuff to Windows XP and Linux (Ubuntu) all with the same release version of OOo. And at these platforms, everything was working as expected. So this seems to be a PPC platform bug. I noticed one difference with PPC: While under Windows and Linux there was <auto> in the ID field, it was empty under PPC. Trying to manually set a value in the PPC version did not work. I hope, you may confirm this :-) Kind regards Christian
I've had similar problems in the past where I spent hours trying to figure out why my data was not editable (cf. https://bugzilla.novell.com/show_bug.cgi?id=444129). Maybe we can figure this one out together. I think it would be best if you uploaded a sanitized MySQL dump and your ODB file here so others can try to confirm or refute the problem.
@ steinsuppe, loria can you confirm the problem of the reporter on MacOSX/PPC This problem seems to be a Mac/PPC Problem only
I have dumped the sql database. Unfortunately my brother has removed the odb file, which used this database :-( Hope the dump is enough. I tried more than once to create a OOo-base document, so the removed one is nothing special on this reported bug. I can not find an upload field here, so I paste the sql-dump here: I had done the inserts with the windows OOo version, which is working ============================================================================== -- MySQL dump 10.11 -- -- Host: localhost Database: kanzlei -- ------------------------------------------------------ -- Server version 5.0.51a-3ubuntu5.3 /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8 */; /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */; /*!40103 SET TIME_ZONE='+00:00' */; /*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */; /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */; /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; /*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */; -- -- Current Database: `kanzlei` -- CREATE DATABASE /*!32312 IF NOT EXISTS*/ `kanzlei` /*!40100 DEFAULT CHARACTER SET utf8 */; USE `kanzlei`; -- -- Table structure for table `Tabelle1` -- DROP TABLE IF EXISTS `Tabelle1`; SET @saved_cs_client = @@character_set_client; SET character_set_client = utf8; CREATE TABLE `Tabelle1` ( `ID` int(11) NOT NULL auto_increment, `Name` varchar(50) default NULL, `Vorname` varchar(50) default NULL, `Str` varchar(50) default NULL, PRIMARY KEY (`ID`) ) ENGINE=MyISAM AUTO_INCREMENT=6 DEFAULT CHARSET=utf8; SET character_set_client = @saved_cs_client; -- -- Dumping data for table `Tabelle1` -- LOCK TABLES `Tabelle1` WRITE; /*!40000 ALTER TABLE `Tabelle1` DISABLE KEYS */; INSERT INTO `Tabelle1` VALUES (3,'Mustermann','Hans','Muster Str'),(4,'Schmidt','Hugo','Lala Weg'); /*!40000 ALTER TABLE `Tabelle1` ENABLE KEYS */; UNLOCK TABLES; /*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */; /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; /*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */; /*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */; /*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */; -- Dump completed on 2008-11-14 11:44:18
Unfortunately i never worked with mysql or OOo database. I tried now several times to reproduce the procedure but get no worthy results -- i'm sorry for that.
Did you try JDBC instead of ODBC? Maybe that will work for you. FWIW, I can not reproduce this with JDBC on Ubuntu, but you already said that Ubuntu was working fine for you as well.
This seems to be a MacOSX problem only. Steinsuppe only told that he can't confirm the reported bug. Please notice the reported plattform. And nobody knows if this works with JDBC driver under MacOSX/PPC before anyone test it. thanks
I only tried ODBC, not JDBC (I do not know, if the PPC has a JDBC drier; if not, where to get one). And yes, this problem only occurs on PPC not Windows, not Ubuntu (Linux). All three testes with ODBC. But ODBC should do fine, shouldn´t it?
Just a quick note from me. Tested with the older 3.51 ODBC drivers from MySQL on INTEL Mac and this scenario seems to work. Tested with both ODBC drivers v. 5.1.5 and 3.51 on PPC and the same scenario DID NOT work. Issue confirmed. Haven't looked at any logs though yet. (Try to do it this evening.) As to where to get ODBC/JDBC drivers for MySQL: - http://dev.mysql.com/downloads/connector/odbc/5.1.html - http://dev.mysql.com/downloads/connector/j/5.1.html
Hi all, Mac OSX 10.6.6 Snow Leopard OOo 3.3.0 final MyODBC : 5.1.8 MySQL Server : 5.1.50 MySQL Community Server I have a similar problem. If necessary, I will open a new bug report. I have an ODB file that uses the myodbc connector to connect to the server containing pre-established tables that have been working for years. When I open this file, and click on the Tables icon, I am asked for the password. I enter the password, the dialog disappears, but then no tables are displayed in the Tables list. If I want to create a new table, I can, and it is stored on the server, under the schema that I select from the dropdown list upon Save Table. However, the newly created table is not visible in the Table list. If I quit OOo completely and then restart it, re-open the ODB file, and reconnect to the database, I still can not see the table I created. However, if I connect to the mysql server via the CLI client using the same connection ID/pwd, I can see the table I just created, and I can add data to it !!! Furthermore, the data do not show up in the OOo ODB even when I go through the whole process of shutting down, restarting and reopening the ODB file again. If this is the same bug as for PPC, then the platform needs to be changed to Mac OSX all, as I'm on OSX Intel, but it appears I can no longer alter these things. Consequently, for me ODBC connectivity is extremely broken on OSX. I have another separate bug report for the Actual Technologies ODBC Driver which also continues to not display information contained in the tables of my database. Alex
All these versions are out-to-date. Please use the native driver for MySQL: https://extensions.openoffice.org/en/project/mysql-driver-apache-openoffice Works fine with AOO and MacOS