Bug #12390 No database update, for successful update instructions in ODBC log
Submitted: 4 Aug 2005 20:10 Modified: 30 May 2013 7:44
Reporter: Luc Michaud Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S2 (Serious)
Version:3.51.11 OS:Windows (windows XP)
Assigned to: Bogdan Degtyariov CPU Architecture:Any

[4 Aug 2005 20:10] Luc Michaud
Description:
Hi all,

       I am trying to update the following tables using MySql 4.0.20a-nt with MySQL ODBC 3.51.11-2 on Windows XP prof. version 2002 SP1 or Windows 2003.
       
       CREATE TABLE adm_current_date (effective_date date NOT NULL default '0000-00-00', PRIMARY KEY  (effective_date)
                                      ) TYPE=MyISAM;

       The following ODBC log, is produce, by the call of a BBX program.

       
...       
BOOT            e38-c1c	ENTER SQLPrepare 
		HSTMT               00BA1F80
		UCHAR *             0x00B81F78 [      -3] "TRUNCATE TABLE adm_current_date\ 0"
		SDWORD                    -3

BOOT            e38-c1c	EXIT  SQLPrepare  with return code 0 (SQL_SUCCESS)
		HSTMT               00BA1F80
		UCHAR *             0x00B81F78 [      -3] "TRUNCATE TABLE adm_current_date\ 0"
		SDWORD                    -3
...
BOOT            e38-c1c	ENTER SQLPrepare 
		HSTMT               00BA1F80
		UCHAR *             0x00B82008 [      -3] "INSERT INTO adm_current_date VALUES ('2005/08/04')\ 0"
		SDWORD                    -3

BOOT            e38-c1c	EXIT  SQLPrepare  with return code 0 (SQL_SUCCESS)
		HSTMT               00BA1F80
		UCHAR *             0x00B82008 [      -3] "INSERT INTO adm_current_date VALUES ('2005/08/04')\ 0"
		SDWORD                    -3

BOOT            e38-c1c	ENTER SQLNumResultCols 
		HSTMT               00BA1F80
		SWORD *             0x01311A78

BOOT            e38-c1c	EXIT  SQLNumResultCols  with return code 0 (SQL_SUCCESS)
		HSTMT               00BA1F80
		SWORD *             0x01311A78 (0)

BOOT            e38-c1c	ENTER SQLFreeStmt 
		HSTMT               00BA1F80
		UWORD                        1 <SQL_DROP>

BOOT            e38-c1c	EXIT  SQLFreeStmt  with return code 0 (SQL_SUCCESS)
		HSTMT               00BA1F80
		UWORD                        1 <SQL_DROP>
		

                The corresponding mySql log includes no trace of the truncate and insert instructions.		
                
		MySql, Version: 4.0.20a-nt-log, started with:
TCP Port: 3306, Named Pipe: MySQL
Time                 Id Command    Argument
050804 10:14:29	      1 Connect     ODBC@derver_name on database
050804 10:14:30	      1 Quit       

                If I use mysql client, I see the adm_current_date table with no changes.
                
                If I use ODBC 3.51.8, the ODBC log is similar, the MySQL log includes the truncate and insert instructions, and the database is update.  

                The probleme append with other tables with other data type.
                
                I need to use version 3.51.11 because, that version solved an important speed problem, when using Cognos series for BI reporting.

bye,

How to repeat:
execute the BBX program
[5 Aug 2005 8:31] Vasily Kishkin
Where can I find out and download BBX ?
[5 Sep 2005 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[27 Sep 2005 17:31] Luc Michaud
Finaly,
         A zip file with all information to repeat the case.  Start with de README.rtf.
[28 Sep 2005 7:54] Vasily Kishkin
Sorry...I can't find any zip file. Where did you upload the file ?
[28 Sep 2005 12:27] Luc Michaud
I do not know what append.

However, there is the file.

Luc
[1 Oct 2005 13:12] Valeriy Kravchuk
There is still no file to repeat the described behavior. Please, send it using the File tab, but remember about 200 Kb limit for file size. You may send your files separately.
[3 Oct 2005 13:10] Luc Michaud
Logs and configuration ODBC 3.51.8 test

Attachment: CASE_12390_log ODBC 3.51.8.zip (application/x-zip-compressed, text), 90.34 KiB.

[3 Oct 2005 13:11] Luc Michaud
Log and configuration ODBC 3.51.11-2 test

Attachment: CASE_12390_log ODBC 3.51.11-2.zip (application/x-zip-compressed, text), 185.77 KiB.

[3 Oct 2005 13:12] Luc Michaud
Log and configuration ODBC 3.51.11 test

Attachment: CASE_12390_log_ODBC 3.51.11.zip (application/x-zip-compressed, text), 185.79 KiB.

[5 Oct 2005 19:18] Luc Michaud
I split the file...
[7 Oct 2005 10:46] Vasily Kishkin
Sorry...I am not avaible to reproduce the bug on Visual Pro5. I created C program,  but I was not able to reproduce the bug. Could you please create and attach some test case on C.
[7 Oct 2005 14:45] Luc Michaud
I am not set up for C programming.

However, we can help you setup and run VisualPro5.

In another way, we will try to generate a log of the exact instruction use by BBX.  This information may be useful to generate a C test.
[12 Oct 2005 8:09] Vasily Kishkin
Please , try to generate a log of the exact instruction use by BBX.  I will generate a C test.
[13 Nov 2005 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[30 May 2013 7:44] Bogdan Degtyariov
I'm closing this bug because I can not continue without feedback from the reporter. If you have new info, please reopen the report.