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

From: Listmail <lists(at)peufeu(dot)com>
To: "Magnus Hagander" <magnus(at)hagander(dot)net>, "Dave Page" <dpage(at)postgresql(dot)org>
Cc: "Andrew Hammond" <andrew(dot)george(dot)hammond(at)gmail(dot)com>, "CAJ CAJ" <pguser(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org, pgsql-www <pgsql-www(at)postgresql(dot)org>
Subject: Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version
Date: 2007-04-11 16:49:18
Message-ID: op.tqmo0ge9zcizji@apollo13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-www

> 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>

... or <item value="3" />

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Albert 2007-04-11 16:49:49 Transactions through JDBC
Previous Message Chris Travers 2007-04-11 16:21:46 Re: The rule question before, request official documentation on the problem

Browse pgsql-www by date

  From Date Subject
Next Message Marc G. Fournier 2007-04-11 17:28:21 Re: [whine] Slow moderation on postgres lists
Previous Message Magnus Hagander 2007-04-11 16:20:46 Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version