| Bug #15264 | Recordset returned ( remote view ) not handling auto increment fields properly | ||
|---|---|---|---|
| Submitted: | 26 Nov 2005 16:41 | Modified: | 2 Jan 2006 10:15 |
| Reporter: | [ name withheld ] | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | Connector / ODBC | Severity: | S2 (Serious) |
| Version: | MySQL ODBC 3.51 Driver | OS: | Windows (XP / Win 2000) |
| Assigned to: | Vasily Kishkin | CPU Architecture: | Any |
[27 Nov 2005 7:54]
Vasily Kishkin
Sorry...I need some test case on C to reproduce the bug. I created test case, but my test case worked fine. Could you please create and attach a test case on C ?
[27 Dec 2005 15:35]
[ name withheld ]
Sorry.... wasn't able to test with C but I've since tested it with SPT (sql pass through) and it works fine. Don't bother with the remote view.
Description: When I use a remote view from Visual Foxpro the recordset returned to the desktop from a Linux Server ( Fedora Core 4 MySQL ) via ODBC 3.51 driver doesn't consistently show the autoincrement column properly. Sometimes it shows as a 0 instead of the proper primary key and fails when you try to refresh the view because the values are different between desktop recordset and the actual file. When you close the view and reopen it is does show the proper value but it doesn't automatically refresh the view as one would expect it to do. How to repeat: (Visual Foxpro Code) use rv_system in 0 go top append blank / insert into rv_system (field1,field2) values ("blah...","dddd") requery() fails.... when the requery() executes.... because client side recordset autoincrement field shows as zero Suggested fix: get the driver to autorefresh recordset when database changes.... if possible.