BUG #2097: Union bug.

From: "Evan Carroll" <personal(at)evancarroll(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #2097: Union bug.
Date: 2005-12-07 06:03:19
Message-ID: 20051207060319.C4903F1CD2@svr2.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 2097
Logged by: Evan Carroll
Email address: personal(at)evancarroll(dot)com
PostgreSQL version: 8.1
Operating system: Linux -- Debian & Ubuntu.
Description: Union bug.
Details:

There apears to be a bug with the Union feature in 8.1. If nothing else it
is an oddity to be recognized. The naming from the result table seems to be
from the first select of the union but it only accepts the second column to
be named identically and misleadingly to the first.

"select col1 as x col1 from tab1 union select * from tab2' and it selects
the first and second column from both tables

IE Here is the exact querry
select fkey_event as F, fkey_event from event_contact UNION select * from
event_object ORDER BY fkey_event;

and here is the header from the outputted table
f | fkey_event
-----+------------

But yet the rows are not the same, they correspond to the natural order of
the sql union, where f is the first col of tbl1+ tbl2, and fkey_event is the
second column of tbl1+tbl2.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jozef Behran 2005-12-07 08:42:35 Re: BUG #2089: Documentation bug: Triggers in plpythonu
Previous Message Bruce Momjian 2005-12-07 04:58:02 Re: BUG #2000: psql does not prompt for password