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

From: Jorge Godoy <jgodoy(at)gmail(dot)com>
To: Listmail <lists(at)peufeu(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: programmatic way to fetch latest release for a given major.minor version
Date: 2007-04-10 16:48:08
Message-ID: 87tzvo6urb.fsf@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-www

Listmail <lists(at)peufeu(dot)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(at)gmail(dot)com>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter Wilson 2007-04-10 17:00:59 Re: programmatic way to fetch latest release for a given major.minor version
Previous Message Dhaval Shah 2007-04-10 15:50:59 Re: Errors during recovery of a postgres. Need some help understanding them...

Browse pgsql-www by date

  From Date Subject
Next Message Peter Wilson 2007-04-10 17:00:59 Re: programmatic way to fetch latest release for a given major.minor version
Previous Message Dave Page 2007-04-10 14:58:12 Re: Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version