From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | lockhart(at)alumni(dot)caltech(dot)edu (Thomas G(dot) Lockhart) |
Cc: | 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:55:23 |
Message-ID: | 199802201655.LAA05498@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> > Added to TODO.
> > > ... In Postgres, a column can be
> > > designated "not null", the default being to allow nulls. In the
> > > default Sybase configuration, it is the other way around. In the
> > > interest of writing cross database compatible code, I try to always
> > > call out columns as either "null" (nulls allowed), or "not null"
> > > (nulls not allowed). Unfortunately, Postgres does not support this
> > > In short, it would be nice if Postgres would take "null" as a type
> > > specifier as well as "not null".
>
> We currently get a shift/reduce parsing conflict on this since NULL can be
> specified in other constraint clauses and since the constraint clauses are
> only whitespace delimited. It might be that this part of the parser can be
> redone, or perhaps the only way around is to restrict the ordering of the
> constraints. But NULL constraint is not SQL92 and free ordering is...
OK, removed from TODO.
--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 1998-02-20 16:56:47 | Re: [HACKERS] Permissions on copy |
Previous Message | Jan Wieck | 1998-02-20 16:52:38 | Re: [HACKERS] triggers, views and rules (not instead) |