| Ticket Hash: | f2c47a01eb564d68c26ace3b881458e872d021da | |||
| Title: | automatic PK indexes with compound keys are not tagged as PK | |||
| Status: | Closed | Type: | Code_Defect | |
| Severity: | Important | Priority: | NextRelease | |
| Subsystem: | Connection | Resolution: | Fixed | |
| Last Modified: | 2013-06-27 00:10:15 | |||
| Version Found In: | 1.0.85.0 | |||
| User Comments: | ||||
anonymous added on 2013-06-03 12:36:20:
Using the generic ADO call dbConnection.GetSchema("Indexes")returns the PK index of a compount key as non PK but unique. The same call works with 1.0.81.0!
mistachkin added on 2013-06-03 18:29:34: Do you have an example SQL schema that demonstrates the behavior you are seeing? mistachkin added on 2013-06-26 22:23:58: I've managed to reproduce the issue here locally. Working on a fix. This fix will be present in the upcoming 1.0.87.0 release. mistachkin added on 2013-06-26 23:42:12: The issue first appeared in release 1.0.85.0. mistachkin added on 2013-06-26 23:53:14: Fixed on trunk by check-in [8d0c39afd2]. | ||||
