From: | Chris Cleveland <ccleveland(at)dieselpoint(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, jcflack(at)acm(dot)org |
Subject: | Re: "Type does not exist" error when returning array of type in non-public schema |
Date: | 2025-02-06 21:06:03 |
Message-ID: | CABSN6VfBKabhFAYeP5TET+r9D1RRkFEt-UPxV4cbo-VrCyHVug@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I solved the problem with:
CREATE FUNCTION myfunc ... RETURNS Token[] ... SET search_path to rdb;
I still don't know why it happens in the first place, though.
On Thu, Feb 6, 2025 at 12:14 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> > On Thu, Feb 6, 2025 at 9:47 AM Chris Cleveland <
> ccleveland(at)dieselpoint(dot)com>
> > wrote:
> >> RETURN "rdb.Token"[], RETURN "rdb.Token[]" all fail.
>
> > Expecting these two to work suggests you need to re-read the section on
> how
> > quoting identifiers works.
>
> I'm wondering if it needs to be "Token". Mixed-case SQL identifiers
> are usually more of a pain than they're worth, frankly.
>
> regards, tom lane
>
--
Chris Cleveland
312-339-2677 mobile
From | Date | Subject | |
---|---|---|---|
Next Message | Chapman Flack | 2025-02-06 21:13:27 | Re: "Type does not exist" error when returning array of type in non-public schema |
Previous Message | Tom Lane | 2025-02-06 21:05:02 | Re: Using Expanded Objects other than Arrays from plpgsql |