Re: RFC: Remove contrib entirely
От | Josh Berkus |
---|---|
Тема | Re: RFC: Remove contrib entirely |
Дата | |
Msg-id | 5568E35B.6060109@agliodbs.com обсуждение исходный текст |
Ответ на | RFC: Remove contrib entirely ("Joshua D. Drake" <jd@commandprompt.com>) |
Список | pgsql-hackers |
On 05/29/2015 02:54 PM, Tom Lane wrote: > Peter Geoghegan <pg@heroku.com> writes: >> The problem here is that these ranges are controlled by a >> decentralized patchwork of national standards bodies, and the ranges >> are always subject to revision. I think that it's egregious that >> contrib/isn imagines it can track that with a static array. > > Well, that module has already been rewritten once (which proves that > there's an audience out there for it). Perhaps somebody will rewrite it > again to support a non-hardwired set of ranges. Now that we have the > concept of an extension configuration table, that'd be one possible > way to fix it ... FWIW, neither of the projects I know of which uses ISBN has had any issues with the range since the 2010 updates. While the ranges can be updated in theory, in practice is happens glacially slowly. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com
В списке pgsql-hackers по дате отправления: