Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id C03484761B6; Tue, 3 Sep 2002 09:16:11 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 713DC476188; Tue, 3 Sep 2002 09:16:10 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id g83DGBZM005033; Tue, 3 Sep 2002 09:16:11 -0400 (EDT) To: Lee Kindness Cc: pgsql-hackers@postgresql.org, pgsql-interfaces@postgresql.org Subject: Re: 7.3 gotchas for applications and client libraries In-reply-to: <15732.36384.130862.855693@kelvin.csl.co.uk> References: <851.1031018040@sss.pgh.pa.us> <15732.36384.130862.855693@kelvin.csl.co.uk> Comments: In-reply-to Lee Kindness message dated "Tue, 03 Sep 2002 11:25:36 +0100" Date: Tue, 03 Sep 2002 09:16:11 -0400 Message-ID: <5032.1031058971@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/147 X-Sequence-Number: 28106 Lee Kindness writes: > CREATE OR REPLACE FUNCTION column_exists(NAME, NAME) RETURNS BOOLEAN AS ' > CREATE OR REPLACE FUNCTION table_exists(NAME) RETURNS BOOLEAN AS ' > Obviously these need attention when our application targets 7.3 (and > thanks for the heads-up), but all changes are localised. They are? What will your policy be about schema names --- won't you have to touch every caller to add a schema name parameter? I'm not averse to trying to push logic over to the backend, but I think the space of application requirements is wide enough that designing general-purpose functions will be quite difficult. regards, tom lane