| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | ocie(at)paracel(dot)com |
| Cc: | 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 14:33:26 |
| Message-ID: | 199802201433.JAA03434@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Added to TODO.
> Here's my output. BTW, this reminds me of a small request (perhaps I
> will write a patch for it myself). 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
> (Please forgive me if this has been added recently, as I have been too
> busy to try out the latest code).
>
> In short, it would be nice if Postgres would take "null" as a type
> specifier as well as "not null".
--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SARZ | 1998-02-20 14:46:46 | triggers, views and rules (not instead) |
| Previous Message | Thomas G. Lockhart | 1998-02-20 13:55:12 | Re: [HACKERS] Re: [BUGS] agregate function sum error |