| From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
| 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 15:42:05 |
| Message-ID: | 34EDA44D.46A66A23@alumni.caltech.edu |
| 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...
- Tom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1998-02-20 15:45:30 | Re: [HACKERS] Permissions on copy |
| Previous Message | Zeugswetter Andreas SARZ | 1998-02-20 15:38:43 | Re: [HACKERS] Who is everyone? |