Re: [PATCHES] New variable server_version_num
От | Jim C. Nasby |
---|---|
Тема | Re: [PATCHES] New variable server_version_num |
Дата | |
Msg-id | 20060801173748.GO40481@pervasive.com обсуждение исходный текст |
Ответ на | Re: [PATCHES] New variable server_version_num (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [PATCHES] New variable server_version_num
|
Список | 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 по дате отправления: