From: | "Gaetano Mendola" <mendola(at)bigfoot(dot)com> |
---|---|
To: | "Stephan Szabo" <sszabo(at)megazone23(dot)bigpanda(dot)com> |
Cc: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Dependence beetwen Function |
Date: | 2002-03-13 09:23:52 |
Message-ID: | 010401c1ca70$cacec160$d28efea9@GMENDOLA2 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"Stephan Szabo" <sszabo(at)megazone23(dot)bigpanda(dot)com> wrote:
> On Tue, 12 Mar 2002, Gaetano Mendola wrote:
>
> > Hi to all
> >
> > Suppose that I have the function A that use the fucntion B.
> > When I drop and reconstruct B I should also reconstruct A.
> > Can I avoid this ?
> > Is a really problem with hundreds of function around.
>
> If you're using 7.2 you can use create or replace function
> rather than drop function followed by create function.
>
Fine. Yesterday with the release 7.1.3 I notice that if a table have a
constraint like this:
CREATE TABLE user_data (
.......
login VARCHAR(64) NOT NULL CHECK ( myFunction(login) ),
......
);
if I drop and recreate the function myFunction
I'm not able to insert data on table user_data.
May be with the version 7.2 this problem not exist anymore
(with the replace feature) but I notice also that if I do a
pg_dump > dump.sql
I have on dump.sql before the creation of tables and after the
creation of functions, in this way the table user_data is not
created ... :-(
I hope that this was fixed in version 7.2
Ciao
Gaetano
--
#exclude <windows>
#include <CSRSS>
printf("\t\t\b\b\b\b\b\b");.
printf("\t\t\b\b\b\b\b\b");
From | Date | Subject | |
---|---|---|---|
Next Message | Jean-Michel POURE | 2002-03-13 11:41:41 | Re: Dependence beetwen Function |
Previous Message | Radu-Adrian Popescu | 2002-03-13 08:55:18 | Re: client connection |