From: | Gary Stainburn <gary(dot)stainburn(at)ringways(dot)co(dot)uk> |
---|---|
To: | Tomasz Myrta <jasiek(at)klaster(dot)net> |
Cc: | Christoph Haller <ch(at)rodos(dot)fzk(dot)de>, pgsql-sql(at)postgresql(dot)org |
Subject: | Upgrade question - was Re: join and dynamic view |
Date: | 2002-12-17 14:57:00 |
Message-ID: | 200212171457.00598.gary.stainburn@ringways.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Christoph Haller | 2002-12-17 15:09:58 | Re: Upgrade question - was Re: join and dynamic view |
Previous Message | Tomasz Myrta | 2002-12-17 14:31:55 | Re: join and dynamic view |