Apache OpenOffice (AOO) Bugzilla – Issue 43529
Crash OOo with mysql table tinyint data insert
Last modified: 2006-05-31 14:29:06 UTC
Tested with MyODBC 3.51.09 Open an ODB file that is linked to a mysql db. Click on Tables, navigate to the table in the table tree, and double click on the table to open it for editing. Navigate in the table to a tinyint unsigned field. The values for these fields are obligatory and by default should be 1. They show up as 0 (another bug report subitted for this problem). Enter any number that fits within the field definition, e.g. 5. Now move down a record with the mouse or cursor button and attempt to edit another record. OOo segfaults, crashes and dumps core. Reproducible.
Setting oooqa and crash keywords
correct prio to 3 see http://www.openoffice.org/scdocs/ddIssues_EnterModify.html#priority for details.
hi, P3 says that it crashes only in exception circumstances. I see nothing exceptional about the circumstances I have described. This should be at least P2, but I set it to P1 because it means you can not test the module's functionality completely. Filling in data in the way described is basic functionality of the dba module, or ins't it ? alex
hmm, cannot reproduce so far (but: On windows, with 3.51.10). Alex, do you mind attaching the mysqldump of a such a table? Which server version do you connect to?
Hi Frank, I've just tested with Beta2.0bc and the problem remains. :-(( Server version : 4.0.20 I can't dump the data in the base because its confidential (I'm a lawyer remember ;-)). What I can do is give you an explain statement of the structure : explain PROFCON +------------+---------------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +------------+---------------------+------+-----+---------+----------------+ | address_id | int(10) unsigned | | PRI | NULL | auto_increment | | LNAME | varchar(35) | YES | | NULL | | | FNAME | varchar(35) | YES | | NULL | | | TITLE | varchar(35) | YES | | NULL | | | COMPANY | varchar(75) | YES | | NULL | | | COADDR1 | varchar(35) | YES | | NULL | | | COADDR2 | varchar(35) | YES | | NULL | | | COADDR3 | varchar(50) | YES | | NULL | | | COCITY | varchar(35) | YES | | NULL | | | COSTATE | varchar(35) | YES | | NULL | | | COZIP | varchar(12) | YES | | NULL | | | COCOUNTRY | varchar(35) | YES | | NULL | | | SALUT | varchar(20) | YES | | NULL | | | CUSTOM3 | varchar(35) | YES | | NULL | | | TEL1 | varchar(40) | YES | | NULL | | | FAX1 | varchar(40) | YES | | NULL | | | FAX2 | varchar(40) | YES | | NULL | | | MOBILE | varchar(40) | YES | | NULL | | | EMAIL | varchar(75) | YES | | NULL | | | WEBSITE | varchar(75) | YES | | NULL | | | NOTES | mediumtext | YES | | NULL | | | Type | tinyint(3) unsigned | | | 0 | | +------------+---------------------+------+-----+---------+----------------+ The SHOW CREATE TABLE command give this : CREATE TABLE `PROFCON` ( `address_id` int(10) unsigned NOT NULL auto_increment, `LNAME` varchar(35) default NULL, `FNAME` varchar(35) default NULL, `TITLE` varchar(35) default NULL, `COMPANY` varchar(75) default NULL, `COADDR1` varchar(35) default NULL, `COADDR2` varchar(35) default NULL, `COADDR3` varchar(50) default NULL, `COCITY` varchar(35) default NULL, `COSTATE` varchar(35) default NULL, `COZIP` varchar(12) default NULL, `COCOUNTRY` varchar(35) default NULL, `SALUT` varchar(20) default NULL, `CUSTOM3` varchar(35) default NULL, `TEL1` varchar(40) default NULL, `FAX1` varchar(40) default NULL, `FAX2` varchar(40) default NULL, `MOBILE` varchar(40) default NULL, `EMAIL` varchar(75) default NULL, `WEBSITE` varchar(75) default NULL, `NOTES` mediumtext, `Type` tinyint(3) unsigned NOT NULL default '0', PRIMARY KEY (`address_id`) ) TYPE=MyISAM The table is DYNAMIC HTH, Alex
Hi Frank, I might add that when I added the field "Type tinyint(3) unsigned not null" via the OOo Table Edit GUI, I set the DEFAULT to be "1". As you can see, OOo or the MyODBC driver has set the DEFAULT to "0" (I've opened another issue for this). However, this doesn't change the behaviour. If I correct the DEFAULT to be "1" with an ALTER TABLE statement from the mysql CLI, OOo still crashes when open the table data for editing, navigate to the column in question and change the value and then move the cursor anywhere or press the "Save changes" button. The message from the console is segfault at line 235 in soffice.bin Alex
I encountered a problem modifying existent rows in your table, which I submitted as issue 44333 (with a stripped version of the table). However, I still cannot reproduce the crash :( Do you mind trying the latest ODBC driver (3.51.11 is most recent on Windows, 3.51.10 on Linux). Wouldn't be the first time that a new MySQL driver fixes such a problem ...
Hi Frank, OK I'll try the latest driver, but the crazy thing is that this problem doesn't exist with 1.1.4. and MyODBC 3.51.09. I'll test with 3.51.10 and let you know. Alex
> OK I'll try the latest driver, but the crazy thing is that this problem doesn't exist with > 1.1.4. and MyODBC 3.51.09. I believe you this, but it doesn't help as long as I can't reproduce the problem :( > I'll test with 3.51.10 and let you know. okay, thanks
I've just tried again with the latest MyODBC driver 3.51.11. Problem is exactly the same. :-( Maybe its fixed in m84, but I haven't got a fast connexion to download it yet. alex
meantime, this sounds pretty much like a duplicate of issue 44333 to me ... Alex, what do you think?
Hi Frank, Yep, certainly looks like it. Closing as duplicate of issue 44333 Alex *** This issue has been marked as a duplicate of 44333 ***
close