| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: NOTICE vs WARNING |
| Date: | 2003-09-02 22:14:54 |
| Message-ID: | 18068.1062540894@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> In fact, I like the criterion that a warning should be raised rather than
> a notice if the effect of the command deviates from what the command
> actually says.
Um. If I construe that literally, then the notices about identifier
truncation need to be warnings. I don't think I like that particular
answer. But as long as you're not too rigid about it, this might be
a reasonable approach.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2003-09-02 22:17:07 | Re: Win32 native port |
| Previous Message | Larry Rosenman | 2003-09-02 22:13:59 | Re: Unixware Patch (Was: Re: Beta2 Tag'd and Bundled ...) |