[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [HACKERS] Data integrity and sanity check
From:       "Rod Taylor" <rbt () zort ! ca>
Date:       2002-03-31 13:16:11
[Download RAW message or body]

There was -- kinda

alter table tab add constraint check (value not null);
--
Rod Taylor

Your eyes are weary from staring at the CRT. You feel sleepy. Notice
how restful it is to watch the cursor blink. Close your eyes. The
opinions stated above are yours. You cannot imagine why you ever felt
otherwise.

----- Original Message -----
From: "Christopher Kings-Lynne" <chriskl@familyhealth.com.au>
To: "Rod Taylor" <rbt@zort.ca>
Cc: "Ferruccio Zamuner" <nonsolosoft@diff.org>;
<pgsql-hackers@postgresql.org>
Sent: Sunday, March 31, 2002 12:31 AM
Subject: Re: [HACKERS] Data integrity and sanity check


> > BTW.  There are good reasons sometimes for having data that
violates
> > current constraints.  The top of a tree may have a static record
with
> > a null parent.  The NOT NULL constraint added after this entry
(via
> > alter table add constraint) should not affect the static record,
so
> > unless you know your data quite well this type of tool wouldn't be
> > particularly useful anyway.
>
> As far as I am aware, there is no alter table add constraint syntax
for
> NOT NULLs atm.  I've submitted a patch that allows alter table/alter
> column set/drop not null though.
>
> Chris
>
>
>
> ---------------------------(end of
broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>


---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org
[prev in list] [next in list] [prev in thread] [next in thread]