List:MySQL ODBC« Previous MessageNext Message »
From:Michael Widenius Date:June 29 1999 4:01am
Subject:ODBC: "Write conflict" from access.
View as plain text  
>>>>> "Steve" == Steve Webb <swebb@stripped> writes:

Steve> Hello.
Steve> I had odbc and access working great together until I upgraded mysql to
Steve> 3.21.33b.  Now, when I try to change something in the database from access, I
Steve> get a "Write Conflict" message.  The dialog box makes it sound like the record
Steve> has been changed since I last read the data and doesn't allow me to change
Steve> the record.

Steve> I tried starting safe_mysqld with the "--old-protocol" option but it didn't
Steve> make any difference. 

Steve> Any ideas?

Steve> I turned on tracing in the odbc driver and I get:

>> do_query
Steve> | >mysql_real_query
Steve> | | enter: handle: 15f3cc
Steve> | | query: Query = "UPDATE Fixed_Assets SET login='test'  WHERE ID = 9 AND
Steve> login = 'crook' AND system_name = 'alpha' AND type = 'cpu' AND description =
Steve> 'PB46A-AA' AND location = 'FL2-2080' AND serial_number = 'KA513VUKN9' AND
Steve> nsf_number IS NULL AND ppe_number = 'PPE000000701' AND po_number = '52391' AND
Steve> vendor = 'DEC' AND date_installed = 19950413000000 AND status IS NULL AND
Steve> timestamp = 19961112000000 AND project = '170113' AND architecture = 'DEC' AND
Steve> operating_system IS NULL"
Steve> | | >free_old_query
Steve> | | <free_old_query
Steve> | <mysql_real_query
Steve> | >mysql_store_result
Steve> | <mysql_store_result
Steve> | >_myfree
Steve> | | enter: ptr: 96c3a28
Steve> | <_myfree
Steve> <do_query
>> SQLRowCount
Steve> | exit: Affected rows: 0
Steve> <SQLRowCount
>> SQLFreeStmt
Steve> | enter: stmt: 15f278  option: 0
Steve> | >mysql_free_result
Steve> | | enter: mysql_res: 0
Steve> | <mysql_free_result
Steve> <SQLFreeStmt
>> SQLFreeStmt
Steve> | enter: stmt: 15f278  option: 1
Steve> | >mysql_free_result
Steve> | | enter: mysql_res: 0
Steve> | <mysql_free_result
Steve> | >_myfree
Steve> | | enter: ptr: 96c2238
Steve> | <_myfree
Steve> | >my_free
Steve> | | my: ptr: 96c3c30
Steve> | <my_free
Steve> <SQLFreeStmt

Hi!

If some of the above fields are DATE field and not DATETIME fields,
then the solution is to upgrade to MySQL 3.22.23b or change all DATE
fields to DATETIME fields!

Regards,
Monty
Thread
ODBC: "Write conflict" from access.Steve Webb26 Jun
  • ODBC: "Write conflict" from access.Michael Widenius29 Jun
    • Re: ODBC: "Write conflict" from access.Steve Webb29 Jun
      • Re: ODBC: "Write conflict" from access.Michael Widenius29 Jun
        • Re: ODBC: "Write conflict" from access.Steve Webb29 Jun
          • Re: ODBC: "Write conflict" from access.Steve Webb29 Jun
            • Re: ODBC: "Write conflict" from access.Steve Webb29 Jun
              • Re: ODBC: "Write conflict" from access. (FIXED IT!)Steve Webb29 Jun