Bug #9009 | ODBC/ADO problem | ||
---|---|---|---|
Submitted: | 7 Mar 2005 8:10 | Modified: | 24 May 2005 8:59 |
Reporter: | Lars Annerstedt | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | Connector / ODBC | Severity: | S2 (Serious) |
Version: | OS: | Windows (Win2000) | |
Assigned to: | Bugs System | CPU Architecture: | Any |
[7 Mar 2005 8:10]
Lars Annerstedt
[17 Mar 2005 18:09]
MySQL Verification Team
Sorry I don't understand well what you meant: Your initial rows are: mysql> select * from test; +----+---------+ | Id | Counter | +----+---------+ | 1 | 3 | | 2 | 3 | | 3 | 0 | | 4 | 3 | | 5 | 3 | +----+---------+ 5 rows in set (0.00 sec) Then in your code you do: queryS = "SELECT Counter FROM TEST WHERE Id = 3" Then you can expect only one row in the result set: id = 3 That it was I got when I did twice your code: mysql> select * from test; +----+---------+ | Id | Counter | +----+---------+ | 1 | 3 | | 2 | 3 | | 3 | 1 | | 4 | 3 | | 5 | 3 | +----+---------+ 5 rows in set (0.00 sec) mysql> select * from test; +----+---------+ | Id | Counter | +----+---------+ | 1 | 3 | | 2 | 3 | | 3 | 2 | | 4 | 3 | | 5 | 3 | +----+---------+ 5 rows in set (0.00 sec)
[17 Mar 2005 19:41]
Lars Annerstedt
Now I'm running 4.1.10a and localhost (at home). Else like before. You stopped too early! I increment the !Counter value so all entries are 3, then when I increment one more time all entries become = 4, if I then increment one more time again all entries will be 5, then 6, then 7, 8, 9, 10 and so on. I have a small VB6-program to verify it.
[17 Mar 2005 19:54]
MySQL Verification Team
Thank you for the feedback. I was able to repeat. mysql> select * from test; +----+---------+ | Id | Counter | +----+---------+ | 1 | 4 | | 2 | 4 | | 3 | 4 | | 4 | 4 | | 5 | 4 | +----+---------+ 5 rows in set (0.00 sec)
[22 Mar 2005 9:20]
Lars Annerstedt
I think You should consider this beeing a serious bug.
[7 Apr 2005 10:35]
Vasily Kishkin
Lars - Can you attach the VB6 testing program to "Files" of bug report system for this bug ?
[7 Apr 2005 11:02]
Lars Annerstedt
Testprogram (need to change ODBC)
Attachment: myBug.zip (application/zip, text), 10.67 KiB.
[17 Apr 2005 11:49]
Lars Annerstedt
I attached my code on Apr 7!
[18 Apr 2005 7:38]
Vasily Kishkin
I've got your test program. Thanks a lot !
[28 Apr 2005 15:23]
Vasily Kishkin
I tried this test on MS SQL and got same result. Maybe It is a bug of VB ? Maybe did I miss some connect options for MS SQL ? Can you write me what options were when you tested on MS SQL ?
[29 Apr 2005 6:41]
Lars Annerstedt
Ok - i'll try, the problem is that I have substituted MS SQL for MySQL (it is much easier to test against MySQL than MS SQL). I've been using MS SQL7 for about 5 years previous to MySQL and the VB-code has been the same. I discovered the 'bug' a while after converting to MySQL. Since it can be avoided by SELECT * or SELECT 'the key' it's not a problem anymore but still a potentional problem for others, not aware of this.
[11 May 2005 7:55]
Lars Annerstedt
Now I also has verified the same behaviour with Microsoft SQL Server. I didn't have quite the same configuration as before, I ran the test in a machine with both SQL7 and SQL2000. Wheter this matters or not I don't know. So from now I also suspect VB/ADO because it was exactly the same behaviour in MySQL as MS SQL.
[24 May 2005 8:59]
Vasily Kishkin
So...if the bug is VB/ADO bug, We are not able to fix it