Bug 59205 - ODBC - incorrect display of default inserted MySQL values using Actual Technologies ODBC driver
Summary: ODBC - incorrect display of default inserted MySQL values using Actual Techno...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
(earliest affected) Master
Hardware: x86-64 (AMD64) macOS (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2013-01-10 17:14 UTC by Alex Thurgood
Modified: 2016-01-19 14:21 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Alex Thurgood 2013-01-10 17:14:34 UTC
Using a locally hosted mysql server.

Table definition :
CREATE TABLE `assistant` (
  `assistant_id` tinyint(3) unsigned NOT NULL AUTO_INCREMENT,
  `assistant` varchar(7) NOT NULL DEFAULT '',
  PRIMARY KEY (`assistant_id`)

Connect to the mysql server using Actual Technologies ODBC driver.
Open up the table for editing.
Insert a char string value into the field assistant.
Move down to next tuple.
Insert a second char sting into the field assistant.
Move up to save the data.

Note that LO displays the autoincrement fields as having a value of 0 (zero) for both entries.
Note that LO displays the chg_date fields as being NULL, with an incorrect date display (see bug #59200)

Close the table.
Re-open the table. The default values are now correctly displayed.

Comment 1 Alex Thurgood 2013-01-10 17:16:48 UTC
Adding Lionel + Julien to CC
Comment 2 Alex Thurgood 2015-01-03 17:38:45 UTC
Adding self to CC if not already on
Comment 3 QA Administrators 2016-01-17 20:03:25 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later)  https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT:

- Update the version field
- Reply via email (please reply directly on the bug tracker)
- Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)


2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword

Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17