Issue 119938 - MySQL-ODBC table open fails in: [MySQL][ODBC 3.51 Diver][mysqld=3.23.52] Optional feature not implemented.
Summary: MySQL-ODBC table open fails in: [MySQL][ODBC 3.51 Diver][mysqld=3.23.52] Opti...
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: 3.4.0
Hardware: PC Windows XP
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2012-06-09 18:35 UTC by martiekr
Modified: 2013-01-29 21:47 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Screen shot of error message (11.36 KB, image/jpeg)
2012-12-12 19:39 UTC, Randy Wester
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description martiekr 2012-06-09 18:35:53 UTC

i could not find this error-message in the archives (i could not even find the word 'feature' related to ODBC messages), but i have this issue:
I opened a MySQL table (with a key field) via ODBC ([MySQL][ODBC 3.51 Diver][mysqld=3.23.52]) and started entering data in it. Then i used the button(s) to sort the tabel on an other column then the key-column. After this buttonclick i got the message: "De gegevens kunnen niet worden geladen" (=Cannot load information). 
The 'More'  button shows: "[MySQL][ODBC 3.51 Diver][mysqld=3.23.52] Optional feature not implemented."
After trying to undo the sorting, closing the table etc. every time i try to open a table that has an key field and contains data gives me this message. I can only open a new (empty) table if it has an key-field but i cannot enter data.
I can open a tabel without a key-field that contains data, in this situation there are no issues.

I'm using the same ODBC connection ([MySQL][ODBC 3.51 Diver][mysqld=3.23.52]) with MS-ACCESS with the same database and the same table, MS-ACCESS works fine and gives no error messages.
So my first conclusion is that it is not a [MySQL][ODBC 3.51 Diver][mysqld=3.23.52] issue (as it works fine on MS-ACCESS) but a OpenOffice-Base issue.

Someone knows the solution? if you need more information, plz ask. 
I will send it then.

Comment 1 Randy Wester 2012-12-12 19:36:35 UTC
I have also run into this same problem in this situation:

 - Running latest available version as of 2012-NOV-23:

 - Accessed an external database application's tables using an ODBC connection.  Some data tables will open, some will not.
  (The application is Sage Quantum 2013, formerly known as the Canadian version of Simply Accounting, which uses MySQL as a back-end application.) 

 - The data tables that will not open contain a date field that appears to contain invalid data when evaluated as a date.

Other things observed:
 - The date field evaluates as 1-Jan-1901 in Microsoft Access, which won't allow editing of the particular record (error message is that the data has changed).  Once the date field has been edited in, the record can be edited.

The date field evaluates as 03/01/1 00:00 in Open Office 3.2, which _will_ allow editing of the date.

The actual data in the date field may be a flag (such as '-1') used by the application program to indicate a null value, or may be an actual null value.  ( I can't tell, my MySQL database powers are limited )

The error message _only_ appears when attempting to open tables that have these date fields in them.  Other tables containing dates, in the same database will open successfully.

This issue does _not_ appear in this situation:
Same situation, except running an older version of Open Office:
Running OpenOffice.Org v. 3.2.9502,
Comment 2 Randy Wester 2012-12-12 19:39:08 UTC
Created attachment 80020 [details]
Screen shot of error message

This is a screenshot of the error message.  If you would like any further information, or if you would like me to perform any additional tests, etc. please contact me.
Comment 3 Randy Wester 2012-12-28 05:12:51 UTC
This is not likely a bug with OpenOffice.  OpenOffice Base is probably asking the MySQL 3.51 ODBC interface for some information that it can't provide, or vice versa.  

Literally, it could be a feature that was not implemented in Mysql 3.51, just as the the error message says.  

It may have been implemented in MySQL 5.2, however using that version is not an option in to interface with the commercial software that is holding the data.