| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
| Cc: | "PostgreSQL Development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: NOTICE vs WARNING |
| Date: | 2003-08-27 04:21:25 |
| Message-ID: | 0c7901c36c52$ade65f60$2800a8c0@mars |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> If it were in fact the characteristic of a NOTICE that you need not pay
> attention to them, why do we have them?
I have often wondered that myself.
> > My thought is that you could turn off NOTICES and not worry.
>
> Well, there are plenty of NOTICE instances that carry a definite need to
> worry, such as identifier truncation, implicitly added FROM items,
> implicit changes to types specified as "opaque", unsupported and ignored
> syntax clauses.
I think that WARNING should be used for ALL things that have been
deprecated. eg. implicit FROM, the opaque business, and definitely
unsupported and ignored synacies.
> I have a slight feeling that these two categories cannot usefully be
> distinguished, but I'm interested to hear other opinions.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Gearon | 2003-08-27 04:33:59 | Re: Replication Ideas |
| Previous Message | Bruce Momjian | 2003-08-27 04:07:29 | Re: NOTICE vs WARNING |