From: | M Sarwar <sarwarmd02(at)outlook(dot)com> |
---|---|
To: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: ERROR: return and sql tuple descriptions are incompatible |
Date: | 2024-05-06 15:05:41 |
Message-ID: | DM4PR19MB59783BF17C30764AE1F8B715D31C2@DM4PR19MB5978.namprd19.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi Scott,
Thanks for the clarification!
Sarwar
________________________________
From: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
Sent: Saturday, May 4, 2024 8:52 PM
To: M Sarwar <sarwarmd02(at)outlook(dot)com>; pgsql-admin(at)lists(dot)postgresql(dot)org <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: ERROR: return and sql tuple descriptions are incompatible
> On May 4, 2024, at 6:38 PM, M Sarwar <sarwarmd02(at)outlook(dot)com> wrote:
>
> Are you suggesting me to use the type either TEXT or some other data type in the below clause of the SQL.
No, but if you want them both in the same column of your output, then one or the other must be cast so the column type is consistent.
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Wienhold | 2024-05-06 19:42:02 | Re: ERROR: return and sql tuple descriptions are incompatible |
Previous Message | M Sarwar | 2024-05-06 15:04:11 | Re: ERROR: return and sql tuple descriptions are incompatible |