From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: New variable server_version_num |
Date: | 2006-07-30 15:27:33 |
Message-ID: | 25385.1154273253@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers pgsql-patches |
David Fetter <david(at)fetter(dot)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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Florian G. Pflug | 2006-07-30 15:29:39 | Re: Questions about update, delete, ctid... |
Previous Message | Martijn van Oosterhout | 2006-07-30 15:04:10 | Re: Questions about update, delete, ctid... |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-07-30 15:44:44 | Re: Going for "all green" buildfarm results |
Previous Message | Zoltan Boszormenyi | 2006-07-30 14:17:52 | Re: Three weeks left until feature freeze |
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2006-07-30 16:04:04 | Re: New variable server_version_num |
Previous Message | David Fetter | 2006-07-30 06:25:44 | Re: New variable server_version_num |