Bug #26651 | MyODBC / ADO Set data type is frequently failing to update when no Primary Key | ||
---|---|---|---|
Submitted: | 26 Feb 2007 23:12 | Modified: | 26 Feb 2007 23:20 |
Reporter: | Erica Moss | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | Connector / ODBC | Severity: | S2 (Serious) |
Version: | 3.51.12 | OS: | Windows (win xp) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[26 Feb 2007 23:12]
Erica Moss
[26 Feb 2007 23:18]
Erica Moss
script unit test fle
Attachment: setbug.vbs (application/octet-stream, text), 3.61 KiB.
[26 Feb 2007 23:19]
Erica Moss
data file
Attachment: setTest.csv (application/vnd.ms-excel, text), 442 bytes.
[27 Feb 2007 7:20]
Erica Moss
Additional Information: It appears that if a Primary Key is added to the data set and the necessary small changes are made to the script file, then this test will complete successfully against the 3.51 drivers, so with this as a workaround I'm lowering the priority of this bug, however the question remains why isn't it able to handle the case where there is no primary key? The worst that should happen here is that the update might not have the desired results because there was more than one match. It shouldn't fail to update at all.
[1 Aug 2007 12:53]
Tonci Grgin
Eric, I think this is either a) SQLPos problem or b) you fail to control your updates depending on schema: http://support.microsoft.com/default.aspx?scid=kb;EN-GB;q190727&GSSNB=1 "Update Criteria" property: The available constants for this property are as follows: adCriteriaKey = 0 Uses only the primary key adCriteriaAllCols = 1 Uses all columns in the recordset adCriteriaUpdCols = 2 (Default) Uses only the columns in the recordset that have been modified adCriteriaTimeStamp = 3 Uses the timestamp column (if available) in the recordset NOTE: Specifying adCriteriaTimeStamp may actually use adCriteriaAllCols method to execute the Update if there is not a valid TimeStamp field in the table. Also, the timestamp field does not need to be in the recordset itself. What do you think?
[3 Dec 2010 3:29]
Bogdan Degtyariov
I had the test (setBug.vbs) successfully passing, but after 3-rd time of sequential re-running the test started to always fail with Connector/ODBC 3.51.27. With 5.1.8 it never passed.