Re: Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version - Mailing list pgsql-www

From Tom Lane
Subject Re: Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version
Date
Msg-id 25896.1176216127@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-www
Alvaro Herrera <alvherre@commandprompt.com> writes:
> It makes sense to store things separately when they have a semantic
> difference.  What we call "major" is the first two digits and dot.  We
> call "minor" to the third digit, and that's all.  We don't have
> "revisions".  This is how it has ever been and we even document it as
> such.  Offering the first two digits separately would be a mistake
> because it causes confusion over what's significant -- the first digit
> by itself is not significant.

While I agree with this position, ISTM that an easy compromise is
available: put both formats into the data.

            regards, tom lane

pgsql-www by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version
Next
From: Dave Page
Date:
Subject: Re: Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version