Bug #36364 | Constraint error when doing Fill schema before Fill Adapter | ||
---|---|---|---|
Submitted: | 27 Apr 2008 8:51 | Modified: | 29 Apr 2008 14:43 |
Reporter: | Anson Chapman | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | Connector / NET | Severity: | S3 (Non-critical) |
Version: | 5.2 Connector/Net | OS: | Windows (XP - SP2) |
Assigned to: | CPU Architecture: | Any | |
Tags: | dataadapter, dataset, DataTable |
[27 Apr 2008 8:51]
Anson Chapman
[29 Apr 2008 14:43]
Reggie Burnett
This can be handled but it is a ton of work. Essentially the server tells me if a field belongs in a key and doesn't change that info just because you didn't include all columns of the key in the query. So, the only way to fix it is to override FillSchema and, for every table in the query, query the indexes from the server and, if all the columns are not present, not mark the column as unique. I'm marking this as won't fix because this bug, as it exists now, won't be fixed. The above solution is a ton of work so I have created a worklog and will target this fix for the 6.0 release. In the meantime I would suggest either not calling FillSchema or disabling constraint checking on the datatable first.