Bug #17016 | I find some problem in MySQL (bugs) - 'update' command in C++ | ||
---|---|---|---|
Submitted: | 1 Feb 2006 16:51 | Modified: | 9 Jan 2008 23:08 |
Reporter: | Hristo Markov | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | Connector / ODBC | Severity: | S2 (Serious) |
Version: | 3.51 | OS: | Windows (Windows) |
Assigned to: | CPU Architecture: | Any |
[1 Feb 2006 16:51]
Hristo Markov
[2 Feb 2006 14:13]
Valeriy Kravchuk
Thank you for a problem report. Please, send the results of SHOW CREATE TABLE TABLE1; statement from mysql client. Are there any data in that table?
[2 Feb 2006 15:07]
Hristo Markov
Hi again, The table from the example that I send to you, have not data. This is only to demonstrate the problem. The command ‘update‘do updates, but the program receives error code and the message is => “Query-based update failed because the row to update could not be found.” The main idea for which I want to try MySQL is that we working with developed from us software technology for very fast producing of big software systems SCUS / System for Creation of Users Systems /, which base on “PROGRAMMING WITHOUT PROGRAMMERS” principle. I want to see how SCUS will work with MySQL database. If you are interesting about SCUS technology please visit our web site www.markovandmarkov.com Greetings, Hristo Markov
[3 Feb 2006 11:44]
Hristo Markov
Before start the example program I executed only the next example commands CREATE TABLE TABLE1 (FIELD1 varchar(1), FIELD2 varchar(2)) INSERT INTO TABLE1 (FIELD1,FIELD2) values ('1','2')
[7 Feb 2006 9:46]
Valeriy Kravchuk
Thank you for the additional information. Please, try to add primary key to your sample table: CREATE TABLE TABLE1 (ID int auto_increment PRIMARY KEY, FIELD1 varchar(1), FIELD2 varchar(2)); INSERT INTO TABLE1 (FIELD1,FIELD2) values ('1','2'); and repeat your test. Inform about the results.
[8 Feb 2006 9:01]
Hristo Markov
I do the test. The problem stays the same.
[27 Feb 2006 16:28]
Jorge del Conde
Thanks for your excellent bug report. I was able to reproduce the behaviour you described using the attached code and create table statements
[26 Aug 2007 19:15]
Kent Boortz
Manager trace log
Attachment: SQL.LOG (application/octet-stream, text), 298.42 KiB.
[9 Jan 2008 23:08]
Jess Balint
I've tested this with Connector/ODBC 5.1 rev990 and I don't see any problem. I've tested both with and without primary key and the "Return matched rows instead of affected rows" option.