| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: cataloguing NOT NULL constraints |
| Date: | 2011-08-06 15:05:58 |
| Message-ID: | 12175.1312643158@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> writes:
> [ wonders what psql's \d will do with NOT NULL constraints ]
I think this might be taking the notion of "it should be backwards
compatible" too far. We're not expecting this patch to not change
the wording of error messages, for instance (in fact, I think a large
part of the point is to add constraint names to not-null errors).
Why would we expect it to not change what \d shows?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2011-08-06 16:05:28 | Re: Reduce WAL logging of INSERT SELECT |
| Previous Message | Peter Geoghegan | 2011-08-06 12:45:01 | Re: Further news on Clang - spurious warnings |