System.Data.SQLite

Login
This project makes use of Eagle, provided by Mistachkin Systems.
Eagle: Secure Software Automation
2013-06-27
00:10 Ticket [f2c47a01eb] automatic PK indexes with compound keys are not tagged as PK status still Closed with 3 other changes artifact: ec9f523436 user: mistachkin
2013-06-26
23:53 Closed ticket [f2c47a01eb]. artifact: 0363d640b3 user: mistachkin
23:50
Modify the index introspection code so that it does not treat PRAGMA table_info 'pk' column values as boolean. Fix for [f2c47a01eb]. check-in: 8d0c39afd2 user: mistachkin tags: trunk
23:42 Ticket [f2c47a01eb] PK indexes of compount keys are not tagged as PK. status still Verified with 5 other changes artifact: d5b15f7be7 user: mistachkin
22:23 Verified ticket [f2c47a01eb]. artifact: 01ae559739 user: mistachkin
2013-06-25
22:24 Pending ticket [f2c47a01eb]. artifact: d6fd5035f7 user: mistachkin
2013-06-03
18:29 Ticket [f2c47a01eb]: 6 changes artifact: a6dc4acabc user: mistachkin
12:36 New ticket [f2c47a01eb]. artifact: 856d9fa10a user: anonymous

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].