Endpoint URL needn't be Unique
Reported by Paul Jones | February 13th, 2011 @ 12:42 PM | in 0.9.3
There are many valid situations where an endpoint URL could be shared between multiple configured endpoints (especially when an endpoint is partition between pairs using constraints). The database currently enforces a unique constraint, which as far as I can see isn't necessary for any of the query/maintenance options. If we don't remove this, then we're going to need a way to "refine" an endpoint within a pair (which I think could be very complex).
Comments and changes to this ticket
-
Ben Hood February 13th, 2011 @ 01:34 PM
Sounds fine to me. If the URL scheme doesn't identify the most atomic
entity possible, then there's no need for it to be unique in the
database. If OTOH we were using URLs to uniquely identify a specific
logical endpoint, then we'd need to extend the concept of what we
consider to be a URL. So for example, if you had logical 2 endpoints
on the with the same HTTP URL that differentiated each other by some
kind of POST parameter, say, and we were using the URL field in the DB
to differentiate between them both, then we'd need to be able to
express this in the URL. Given that we don't, let's just get rid of
the constraint. -
Ben Hood February 13th, 2011 @ 04:26 PM
(from [4d69e4ff54194274ebad8985f90898720e6afccc]) [#186] Don't enforce unique constraint on endpoint url https://github.com/lshift/diffa/commit/4d69e4ff54194274ebad8985f908...
-
Paul Jones February 13th, 2011 @ 04:26 PM
- State changed from “new” to “resolved”
- Assigned user set to “Ben Hood”
Implemented.
-
-
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.
People watching this ticket
Ben Hood
Referenced by
-
186
Endpoint URL needn't be Unique
(from [4d69e4ff54194274ebad8985f90898720e6afccc])
[#186] ...
-
186
Endpoint URL needn't be Unique
(from [3621ae19d11b568e6288c13fc72e0331da794fd1])
Merged ...