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] Implementation proposal descr line
- Previous message (by thread): [db-wg] Implementation proposal descr line
- Next message (by thread): [db-wg] Implementation proposal descr line
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sascha Luck [ml]
dbwg at c4inet.net
Thu Jan 28 15:38:53 CET 2016
On Wed, Jan 27, 2016 at 05:27:44PM +0100, Tim Bruijnzeels wrote: >In this scenario "netname:" and "asname:" would become optional. >And a one time effort is done to remove the attribute where it >has been enforced so-far. This is our preferred option because >not having duplicate possibly inconsistent data will improve >data quality and reduce work. This, absolutely. Having redundant, and potentially conflicting, data in the same dataset is near enough the ultimate crime when it comes to maintaining a database. The argument that it is more convenient for some does not hold water when compared to the risks and effort of maintaining the same data in multiple places in the same object. rgds, Sascha Luck
- Previous message (by thread): [db-wg] Implementation proposal descr line
- Next message (by thread): [db-wg] Implementation proposal descr line
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]