From: | "Christian Marschalek" <cm(at)chello(dot)at> |
---|---|
To: | "'Gregory Wood'" <gregw(at)com-stock(dot)com>, "'Joel Burton'" <jburton(at)scw(dot)org> |
Cc: | "[GENERAL] PostgreSQL" <pgsql-general(at)postgresql(dot)org> |
Subject: | RE: NOTICE: CREATE TABLE will create implicit trigger(s) for FOREIGN KEY check(s) ? |
Date: | 2001-04-26 18:04:37 |
Message-ID: | 000001c0ce7b$5b7ea6a0$0200a8c0@server |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Got it...
It seams those triggers were created to handle the types I used for the
columns: int2 and bytea...
I realy should check out the types section in the postgres docu :))
> -----Original Message-----
> From: Gregory Wood [mailto:gregw(at)com-stock(dot)com]
> Sent: Thursday, April 26, 2001 7:59 PM
> To: Christian Marschalek
> Cc: PostgreSQL-General
> Subject: Re: NOTICE: CREATE TABLE will create implicit
> trigger(s) for FOREIGN KEY check(s) ?
>
>
> > Can anyone tell me what this notice means?
> >
> > NOTICE: CREATE TABLE will create implicit trigger(s) for
> FOREIGN KEY
> > check(s) ?
>
> It means that PostgreSQL will automatically create triggers
> to perform your foreign key checks :)
>
> Seriously though, PostgreSQL has to have some mechanism to
> check that your foreign key values exist (or not), and it
> does that by using a feature already built into PostgreSQL:
> triggers. Nothing you really need to worry about unless you
> are doing something fancy (for instance, disabling all
> triggers on either table to accomplish some action... in such
> a case your foreign key relationship might be broken).
>
> Greg
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2001-04-26 18:05:05 | Re: Struggling to change default data location |
Previous Message | Gregory Wood | 2001-04-26 17:58:35 | Re: NOTICE: CREATE TABLE will create implicit trigger(s) for FOREIGN KEY check(s) ? |