Bug #4432 | Successful status but record not updated | ||
---|---|---|---|
Submitted: | 7 Jul 2004 10:11 | Modified: | 30 May 2013 5:28 |
Reporter: | Nicolas Loechner | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
Version: | 3.51.07 | OS: | Windows (Windows) |
Assigned to: | Matthew Lord | CPU Architecture: | Any |
[7 Jul 2004 10:11]
Nicolas Loechner
[1 Oct 2004 22:59]
Matthew Lord
Dear Sir, Thank you for your bug report! For this kind of general, application layer, row editing to work the table will need a primary key so that each row can be uniquely identified. Try making the unique index the primary key or making the primary key be a combination of two or more of the other indexed columns. The main difference between a primary key and a unique index is that a primary key does not allow null values as it needs to be truly unique and cannot allow multiple null or undefined values. Best Regards
[14 Feb 2005 22:54]
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 5:28]
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.