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

From Magnus Hagander
Subject Re: [pgsql-www] programmatic way to fetch latest release for a given major.minor version
Date
Msg-id 20070411180722.GC7401@svr2.hagander.net
Whole thread Raw
In response to Re: [pgsql-www] programmatic way to fetch latest release for a given major.minor version  (Listmail <lists@peufeu.com>)
List pgsql-general
On Wed, Apr 11, 2007 at 06:49:18PM +0200, Listmail wrote:
>
>
> >If someone wants the schema change, react *now*. Later on we can only
> >append to it, and not change it :)
>
>     Since I like to complain...
>
> <numericversion v1="8" v2="2" v3="3"/>
>
>     Suppose you someday add another dot, or a "b" for beta, wouldn't it
>     be  better to have
>
> <versionlist><item>8</item><item>2</item><item>3</item></versionlist>

IIRC, but not entirely sure, the order of items in XML is not guaranteed.
So you'd need something like
<versionlist><item seq="1">8</item><item seq="2">2</item> etc etc

I'm not sure, but I have some kind of memory of that ;-)


As for beta, we're only going to be listing production versions in this
one. It's there to list the latest available version in each released
series.
And if we add another dot, we can just add a v4="7" attribute. Adding is
not a problem, only modifying.

//Magnus


pgsql-general by date:

Previous
From: "Alberto Molteni"
Date:
Subject: Re: Transactions through JDBC
Next
From: "Merlin Moncure"
Date:
Subject: Re: Dumping part (not all) of the data in a database...methods?