Re: [PATCHES] New variable server_version_num - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: [PATCHES] New variable server_version_num
Date
Msg-id 20060801173748.GO40481@pervasive.com
Whole thread Raw
In response to Re: [PATCHES] New variable server_version_num  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCHES] New variable server_version_num  (David Fetter <david@fetter.org>)
List pgsql-hackers
On Sun, Jul 30, 2006 at 11:27:33AM -0400, Tom Lane wrote:
> David Fetter <david@fetter.org> writes:
> > On Sat, Jul 29, 2006 at 09:44:10PM -0400, Tom Lane wrote:
> >> The correct solution is for client-side libraries to provide the
> >> feature.
>
> > Not if the app is written in SQL, as the bootstrap, regression test,
> > etc. code for modules frequently is.
>
> SQL doesn't really have any conditional ability strong enough to deal
> with existence or non-existence of features.  What are you hoping to
> do, a CASE expression?  Both arms of the CASE still have to parse,
> so I remain unconvinced that there are real world uses.

There's also plpgsql, which afaik has no way to get the version number
(other than slogging though the output of version()).
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: GENERATED ... AS IDENTITY, Was: Re: Feature Freeze
Next
From: David Fetter
Date:
Subject: Re: [PATCHES] New variable server_version_num