From: | Jan Wieck <janwieck(at)yahoo(dot)com> |
---|---|
To: | Rod Taylor <rbt(at)zort(dot)ca> |
Cc: | Ferruccio Zamuner <nonsolosoft(at)diff(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Data integrity and sanity check |
Date: | 2002-04-01 16:14:10 |
Message-ID: | 200204011614.g31GEA929902@saturn.janwieck.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Rod Taylor wrote:
> > 2) re-check any constraint inserted into the database
>
> There should not be any if it was accepted, however if it's a new
> constraint it doesn't get applied to data that already exists. A dump
> and restore will ignore these as well (with good reason).
Please don't make up any answers. If you don't know for sure,
look at the code in question or just don't answer.
PostgreSQL does check all existing data when adding a foreign
key contraint. It skips the check during the restore of a
dump though.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Doug McNaught | 2002-04-01 16:14:52 | Re: NOT IN queries |
Previous Message | Nic Ferrier | 2002-04-01 15:55:32 | NOT IN queries |