Skip site navigation (1) Skip section navigation (2)

Re: 7.3 gotchas for applications and client libraries

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 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2002-09-03 13:21:33
Subject: Re: findoidjoins
Previous:From: Nigel J. AndrewsDate: 2002-09-03 13:14:31
Subject: Re: Memory management question

pgsql-interfaces by date

Next:From: terryDate: 2002-09-03 13:54:01
Subject: Re: pgaccess - where to store the own data
Previous:From: Lee KindnessDate: 2002-09-03 10:25:36
Subject: 7.3 gotchas for applications and client libraries

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group