Re: programmatic way to fetch latest release for a given major.minor version - Mailing list pgsql-general

From Jorge Godoy
Subject Re: programmatic way to fetch latest release for a given major.minor version
Date
Msg-id 87tzvo6urb.fsf@gmail.com
Whole thread Raw
In response to Re: programmatic way to fetch latest release for a given major.minor version  (Listmail <lists@peufeu.com>)
Responses Re: programmatic way to fetch latest release for a given major.minor version  (Peter Wilson <petew@yellowhawk.co.uk>)
List pgsql-general
Listmail <lists@peufeu.com> writes:

>>> 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
>
>     Just pretend that :
>
>     - version = a tuple of integers (a, b, c, ...)
>     - major = (a, b)
>     - minor = (c, ...)
>
>     Besides, that is sortable (unlike strings where 15 < 2) :

But then, floats are as sortable as integers and 8.3 < 15.1...


--
Jorge Godoy      <jgodoy@gmail.com>

pgsql-general by date:

Previous
From: "Dhaval Shah"
Date:
Subject: Re: Errors during recovery of a postgres. Need some help understanding them...
Next
From: Peter Wilson
Date:
Subject: Re: programmatic way to fetch latest release for a given major.minor version