| From: | Andy Fan <zhihuifan1213(at)163(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Better error messages for %TYPE and %ROWTYPE in plpgsql |
| Date: | 2024-02-27 00:40:17 |
| Message-ID: | 87wmqqzqc6.fsf@163.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Per recent discussion[1], plpgsql returns fairly unhelpful "syntax
> error" messages when a %TYPE or %ROWTYPE construct references a
> nonexistent object. Here's a quick little finger exercise to try
> to improve that.
Looks this modify the error message, I want to know how ould we treat
error-message-compatible issue during minor / major upgrade. I'm not
sure if my question is too inconceivable, I ask this because one of my
patch [1] has blocked on this kind of issue [only] for 2 months and
actaully the error-message-compatible requirement was metioned by me at
the first and resolve it by adding a odd parameter. Then the odd
parameter blocked the whole process.
[1] https://www.postgresql.org/message-id/87r0hmvuvr.fsf@163.com
--
Best Regards
Andy Fan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-02-27 00:54:05 | Re: Better error messages for %TYPE and %ROWTYPE in plpgsql |
| Previous Message | Andrew Dunstan | 2024-02-27 00:20:46 | Re: WIP Incremental JSON Parser |