Configuration data doesn't support domains consistently in primary keys
Reported by John Wright | August 17th, 2011 @ 04:20 PM
For example, the pair table's primary key is just
the pair_key column, so can't be scoped to a domain.
Its key should really be (domain, pair_key). This also
applies to the endpoint table, and other dependent
tables.
Comments and changes to this ticket
-
Paul Jones August 24th, 2011 @ 05:39 AM
- State changed from “new” to “open”
- Assigned user changed from “John Wright” to “Paul Jones”
I'm going to have a crack at getting this one fixed.
-
Ben Hood August 24th, 2011 @ 06:32 AM
(from [12b0b0ab0c0a5cc86abd8b48312b8884b71cafc0]) [#348] Include domain in primary key for pairs and endpoints. https://github.com/lshift/diffa/commit/12b0b0ab0c0a5cc86abd8b48312b...
-
Paul Jones August 24th, 2011 @ 06:43 AM
- State changed from “open” to “resolved”
- Assigned user changed from “Paul Jones” to “Ben Hood”
Ready for QA. The migration is probably very Derby specific, but that probably isn't too much of an issue at this point.
-
Ben Hood August 24th, 2011 @ 08:21 AM
(from [f7f180697ebd2b279b83972f992f730743e6b028]) Merge pull request #68 from lshift/348
[#348] Include domain in primary key for pairs and endpoints. https://github.com/lshift/diffa/commit/f7f180697ebd2b279b83972f992f...
-
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
Ben Hood