Content-Type: text/plain;
  charset="iso-8859-1"
From: Gary Stainburn <gary.stainburn@ringways.co.uk>
Organization: Ringways Garages Ltd
To: Tomasz Myrta <jasiek@klaster.net>
Subject: Upgrade question - was Re: join and dynamic view
Date: Tue, 17 Dec 2002 14:57:00 +0000
User-Agent: KMail/1.4.3
Cc: Christoph Haller <ch@rodos.fzk.de>, pgsql-sql@postgresql.org
References: <3DFF2A7B.B26EEF93@rodos.fzk.de>
	<200212171411.53358.gary.stainburn@ringways.co.uk>
	<3DFF355B.4000905@klaster.net>
In-Reply-To: <3DFF355B.4000905@klaster.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200212171457.00598.gary.stainburn@ringways.co.uk>

On Tuesday 17 Dec 2002 2:31 pm, Tomasz Myrta wrote:
> Gary Stainburn wrote:
> > I found that the compile error complaining about the 'OR' was on the
> >
> > CREATE OR REPLACE FUNCTION
> >
> > line.  I removed the 'OR REPLACE' and everything worked fine.
>
> OR REPLACE is since postgres 7.2

That explains it - the server I'm developing on is quite old - I didn't 
realise how old.  I'm about to do an upgrade from 7.1.3 to 7.2.1-5 over 
christmas in fact.

Will I need to dump/restore the database for this upgrade?

>
> > Also I had to change the returns to 'opaque' and 'return 0' to 'return
> > null'
>
> In this case it's ok to "return null", but if you create "before"
> trigger you shoud "return new", because "return null" forces postgres
> not to insert any data.
>
> Tomasz Myrta

-- 
Gary Stainburn
 
This email does not contain private or confidential material as it
may be snooped on by interested government parties for unknown
and undisclosed purposes - Regulation of Investigatory Powers Act, 2000