Uploaded image for project: 'MariaDB Connector/ODBC'
  1. MariaDB Connector/ODBC
  2. ODBC-119

MariaDB connected through ODBC does not match MSAccess table

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.2
    • Fix Version/s: 2.0.16, 3.0.3
    • Component/s: General
    • Labels:
      None
    • Environment:
      Windows 10

      Description

      Hello,

      I am using the connector version 3.02.

      Why do my MariaDB tables not match what I get in MSACCESS?

      I will show the top three records here:

      MariaDB:
      '327', '110', '6704', '2017-10-10 12:53:07', NULL
      '326', '110', '6689', '2017-09-28 16:07:55', NULL
      '325', '110', '6688', '2017-09-28 16:07:49', NULL

      MSAccess:
      325 110 6688 28.09.2017 16:07:49
      325 110 6688 28.09.2017 16:07:49
      325 110 6688 28.09.2017 16:07:49

      Please pay attention to the first column.

      Here is the create statement for my table on MariaDB:

      CREATE TABLE `ctbl_compoundbundles_compounds` (
      `BundleCompoundID` int(11) NOT NULL AUTO_INCREMENT,
      `CompoundBundleID` int(11) NOT NULL,
      `CompoundID` int(11) NOT NULL,
      `timestamp` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp(),
      `DateTime_ODBCWriteConflict_Fix` datetime DEFAULT NULL,
      PRIMARY KEY (`BundleCompoundID`),
      UNIQUE KEY `UNIQUE` (`CompoundBundleID`,`CompoundID`),
      KEY `INDEX` (`BundleCompoundID`)
      ) ENGINE=InnoDB AUTO_INCREMENT=328 DEFAULT CHARSET=latin1;
      SELECT * FROM crystaltrain.ctbl_compoundbundles_compounds;

        Attachments

          Activity

            People

            Assignee:
            Lawrin Lawrin Novitsky
            Reporter:
            ipk Ingo Korndoerfer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: