From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Lee Kindness <lkindness(at)csl(dot)co(dot)uk> |
Cc: | pgsql-hackers(at)postgresql(dot)org, pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: 7.3 gotchas for applications and client libraries |
Date: | 2002-09-03 13:16:11 |
Message-ID: | 5032.1031058971@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-interfaces |
Lee Kindness <lkindness(at)csl(dot)co(dot)uk> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-09-03 13:21:33 | Re: findoidjoins |
Previous Message | Nigel J. Andrews | 2002-09-03 13:14:31 | Re: Memory management question |
From | Date | Subject | |
---|---|---|---|
Next Message | terry | 2002-09-03 13:54:01 | Re: pgaccess - where to store the own data |
Previous Message | Lee Kindness | 2002-09-03 10:25:36 | 7.3 gotchas for applications and client libraries |