Re: programmatic way to fetch latest release for a given major.minor version

Поиск
Список
Период
Сортировка
От Magnus Hagander
Тема Re: programmatic way to fetch latest release for a given major.minor version
Дата
Msg-id 20070410111509.GF24976@svr2.hagander.net
обсуждение исходный текст
Ответ на Re: programmatic way to fetch latest release for a given major.minor version  (Dave Page <dpage@postgresql.org>)
Ответы Re: programmatic way to fetch latest release for a given major.minor version
Re: programmatic way to fetch latest release for a given major.minor version
Список pgsql-general
On Tue, Apr 10, 2007 at 12:03:44PM +0100, Dave Page wrote:
> Magnus Hagander wrote:
> > On Tue, Apr 10, 2007 at 09:52:52AM +0100, Dave Page wrote:
> >> Magnus Hagander wrote:
> >>> 2) Create a new file with a specific schema. Something like:
> >>> <version>
> >>>  <version major="8.2" minor="8.2.3" />
> >>>  <version major="8.1" minor="8.1.8" />
> >>> </version>
> >>> This is the most lightweight solution.
> >> More like:
> >>
> >> <versions>
> >>   <version major="8" minor="2" revision="3" />
> >>   <version major="8" minor="1" revision="8" />
> >> </versions>
> >
> > But that doesn't reflect our terminology. Per our own terminology, bioth
> > 8.1 and 8.2 are major versions. Not only is that what we've been saying for
> > years, we even documented it at
> > http://www.postgresql.org/support/versioning.
>
> Yeah yeah, but terminology aside, having 2 or three digits in each
> attribute is just wrong!

Terminology aside, why? The unit is "8.1" not "8" and "1". It makes no
sense to say you're on version 8, in the given context, so why should the
XML data pretend there is?

//Magnus


В списке pgsql-general по дате отправления:

Предыдущее
От: Dave Page
Дата:
Сообщение: Re: programmatic way to fetch latest release for a given major.minor version
Следующее
От: Dave Page
Дата:
Сообщение: Re: programmatic way to fetch latest release for a given major.minor version