This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] mntner with misleading primary key
- Previous message (by thread): [db-wg] mntner with misleading primary key
- Next message (by thread): [db-wg] mntner with misleading primary key
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at instituut.net
Wed Jul 1 21:00:44 CEST 2020
On Wed, Jul 1, 2020, at 20:52, Gert Doering wrote: > On Wed, Jul 01, 2020 at 07:36:53PM +0200, Cynthia Revström via db-wg wrote: > > I am not sure how feasible the mandatory "-mnt" would be at this point tbh. > > I can easily think of at least 2 maintainers that are actually used that I > > see quite often that wouldn't fit that pattern. > > It would annoy me a bit, because all our stuff is under SPACENET-N and > SPACENET-P ("networks and person objects"). And all tools. > > Of course it is doable, but... why? Convince me :-) As I understand the conversation, the one option on the table to discuss is how to deal with primary keys that clash with other scopes of context, specifically autnums. Of those only 26 exist SPACENET-P does not look like an AS number so isn't an issue and doesn't need to change. Kind regards, Job
- Previous message (by thread): [db-wg] mntner with misleading primary key
- Next message (by thread): [db-wg] mntner with misleading primary key
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]