Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 152C49FB654; Tue, 10 Apr 2007 08:35:48 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 04925-02; Tue, 10 Apr 2007 08:35:40 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from developer.pgadmin.org (developer.pgadmin.org [63.246.23.140]) by postgresql.org (Postfix) with ESMTP id 84ED89FB652; Tue, 10 Apr 2007 08:35:44 -0300 (ADT) Received: from [172.24.32.110] ([62.232.55.118]) (authenticated bits=0) by developer.pgadmin.org (8.13.8/8.13.8) with ESMTP id l3ABXErG029681 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Apr 2007 11:33:16 GMT Message-ID: <461B768A.8070402@postgresql.org> Date: Tue, 10 Apr 2007 12:35:38 +0100 From: Dave Page User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221) MIME-Version: 1.0 To: Magnus Hagander CC: Andrew Hammond , CAJ CAJ , pgsql-general@postgresql.org, pgsql-www Subject: Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version References: <1176155240.221125.319880@y80g2000hsf.googlegroups.com> <467669b30704091526v79ae044boe7217cc0777dce1f@mail.gmail.com> <5a0a9d6f0704091534i4e4af90co2dad0e9e0b60efee@mail.gmail.com> <461B3E6A.8080007@postgresql.org> <20070410081558.GB24976@svr2.hagander.net> <461B5064.8010004@postgresql.org> <20070410101852.GC24976@svr2.hagander.net> <461B6F10.3040800@postgresql.org> <20070410111509.GF24976@svr2.hagander.net> In-Reply-To: <20070410111509.GF24976@svr2.hagander.net> X-Enigmail-Version: 0.94.1.2 OpenPGP: url=http://www.pgadmin.org/pgp/davepage.pgp Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/23 X-Sequence-Number: 11773 Magnus Hagander wrote: > 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? Because serving the data in the decomposed format gives the consumer the maximum flexibility to do as they wish with the data. I find it hard to see why, as a relational database guy, you'd want to offer the data as "8.1", "8.1.3" etc. when you can just give the three parts separately and allow people to check whatever they need without having to chop up strings! Imagine wanting to display only the details of the 8.x releases on a site for example. In your schema, you'd have to use a substring match on an attribute value to filter out 6.x and 7.x. Regards,D ave.