+1 On Mon, Oct 8, 2018 at 3:51 PM Robert Butts <[email protected]> wrote:
> +1. All the +1s. > > I do think there are some "real" IDs we might have to keep, where an ID is > the real, only Candidate Key (maybe regex?), But for everything else, using > the real Candidate Key will be _drastically_ easier to work with. It'll > make posting a DS or Server without prior info 1 req instead of like 7. > > On Mon, Oct 8, 2018, 15:44 Dan Kirkwood <[email protected]> wrote: > > > Hi all.. we've discussed the possibility of moving the major version > of > > the Traffic Ops API at some point in the (hopefully near) future. When > > that does happen, I'd like to propose that the change include > elimination > > of using foreign key ids (from the "id" field) and instead reference > using > > a different unique key. > > > > Most tables have such a unique key: name, username, hostname, etc, and > the > > API should be able to be upgraded to handle most cases fairly easily. > > > > Of course, more details would need to be worked out including maintaining > > an upgrade path and ensuring no functionality is lost, but wanted to get > > the idea out there for discussion. > > > > thanks.. Dan > > >
