From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Robson Paniago de Miranda <robson(at)mpdft(dot)gov(dot)br> |
Cc: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, ocie(at)paracel(dot)com, vadim(at)sable(dot)krasnoyarsk(dot)su, meskes(at)topsystem(dot)de, Andreas(dot)Zeugswetter(at)telecom(dot)at, pgsql-hackers(at)hub(dot)org |
Subject: | Re: [HACKERS] Subselects and NOTs |
Date: | 1998-02-20 16:51:31 |
Message-ID: | 34EDB492.A96ED6FE@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> I think my original patch about NOT NULL constraint allows this type of
> construction. However, thinks have changed in the parser since I made
> this patch, and now seems that a construction like
> CREATE TABLE a (b int constraint not_null NOT NULL)
> is now valid (I only saw gram.y - maybe I'm wrong). I can make the
> patches to allow NULL, but I only want a litte help: is the name of this
> type of constraint beeing saved anywere?
Yes, I think so.
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 1998-02-20 16:52:38 | Re: [HACKERS] triggers, views and rules (not instead) |
Previous Message | Robson Paniago de Miranda | 1998-02-20 16:51:22 | Re: [HACKERS] Subselects and NOTs |