| Ticket Hash: | 6d5cdbd91dc4718654c87e077cf72325484a8b35 | ||
| Title: | VS-TableDesigner creates wrong foreign key constraints | ||
| Status: | Review | Type: | Feature_Request |
| Severity: | Important | Priority: | Medium |
| Subsystem: | VsDesigner | Resolution: | Open |
| Last Modified: |
2014-11-08 02:04:20 10.66 years ago |
Created: |
2014-11-04 10:10:22 10.67 years ago |
| Version Found In: | 1.0.94 | ||
| User Comments: | ||||
anonymous added on 2014-11-04 10:10:22:
If you add more than 1 foreign key in one "session" (before saving/generating change script) then all separate foreign keys get mangled into one single (silly) line:
CONSTRAINT [FK_FileHashHistory_-1_-1] FOREIGN KEY ([ParentHashId], [ChildHashId]) REFERENCES [Hashes] ([Id], [Id])
should have been:
CONSTRAINT [FK_FileHashHistory_1_0] FOREIGN KEY ([ParentHashId]) REFERENCES [Hashes] ([Id]),
CONSTRAINT [FK_FileHashHistory_2_0] FOREIGN KEY ([ChildHashId]) REFERENCES [Hashes] ([Id])
This even happens when targeting different tables: Then only the first table is used at all.
(VS2013U3)
mistachkin added on 2014-11-05 18:56:48: The VS design-time components do not necessarily support all features of the SQLite core library. Changing to feature request. | ||||