Re: Reported type mismatch improperly
| От | Andy Fan |
|---|---|
| Тема | Re: Reported type mismatch improperly |
| Дата | |
| Msg-id | CAKU4AWotg2V6uaZU-idMVuJ41nZ=QsUtKcKHcjnu=X7RoJNc_Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Reported type mismatch improperly (Andy Fan <zhihui.fan1213@gmail.com>) |
| Список | pgsql-bugs |
On Sun, Jul 19, 2020 at 10:25 AM Andy Fan <zhihui.fan1213@gmail.com> wrote:
On Sat, Jul 18, 2020 at 12:28 PM David G. Johnston <david.g.johnston@gmail.com> wrote:On Friday, July 17, 2020, Andy Fan <zhihui.fan1213@gmail.com> wrote:On Sat, Jul 18, 2020 at 12:23 AM David G. Johnston <david.g.johnston@gmail.com> wrote:- which they still need to be aware of even though this patch removes one situation where it matters.Can you provide an example of this? If it is not very troublesome, I'd like to fix both.Nothing concrete off hand, more of an impression.David J.Improve some comments and test cases, and submit it https://commitfest.postgresql.org/29/2653/ .
I have withdrawn the patch in commitfest since the current solution is bad. To fix it I have
to spend more time on tranformExpr part. I can open a new one if I get it really fixed. Now
I have let the user cast the null to int explicitly.
Best Regards
Andy Fan
В списке pgsql-bugs по дате отправления: