| From: | Rumpi Gravenstein <rgravens(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, PostgreSQL <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array |
| Date: | 2025-08-06 21:39:33 |
| Message-ID: | CAEpg1wCuZ5DgA_oj=pY8BUnsRP_7Lk24xXwjzp-Atw1-Uir-AA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
That having a table and function with similar names causes this problem is
a bug.
Going forward I'll be sure to avoid the problem.
On Wed, Aug 6, 2025 at 5:35 PM David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Wednesday, August 6, 2025, Rumpi Gravenstein <rgravens(at)gmail(dot)com>
> wrote:
>
>> Here's a reproducible test case that causes the problem in different
>> schemas. The issue appears to be related to creating a table and a
>> function that has the same name as the table with a prepended underscore.
>>
>
> Don’t do that. Naming a function (action) and table (noun) the same seems
> unwise anyway, underscores or no.
>
> David J.
>
>
--
Rumpi Gravenstein
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-08-06 21:46:32 | Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array |
| Previous Message | David G. Johnston | 2025-08-06 21:35:24 | Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array |