| From: | Tuckheng <Tuckheng(at)vads(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: "Relation does not exist" error |
| Date: | 2001-11-09 02:26:22 |
| Message-ID: | 086C73F91FD3D41182E80090275CD0BA010C1DE5@exchange1.vads.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
Thanks a bundle. Applied your suggestion and it works :-)
Regards,
Tuck Heng
VADS BHD
03 - 7712 8330
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Thursday, November 08, 2001 10:35 PM
To: Tuckheng
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] "Relation does not exist" error
Tuckheng <Tuckheng(at)vads(dot)com> writes:
> I encountered this error when trying to run a SELECT statement from within
a
> Perl program. Would appreciate if someone could help shed some light on
what
> may be causing this or how it can be resolved.
ORDER BY on a UNION result can only refer to column names of the UNION
output columns. Lose the "p." and "s." in the ORDER BY and you'll be
fine.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PIPER,JIM (A-SantaClara,ex1) | 2001-11-09 05:43:02 | MS Client ODBC question |
| Previous Message | Tom Lane | 2001-11-09 01:24:42 | Re: [HACKERS] PostgreSQL v7.2b2 Released |