full outer join bug?

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: pgsql-hackers(at)postgresql(dot)org
Subject: full outer join bug?
Date: 2001-11-18 11:57:39
Message-ID: 20011118205739T.t-ishii@sra.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Here is a report from a user in Japan. I confirmed it happens in
current.

DROP TABLE t1;
CREATE TABLE t1 ( name TEXT, n INTEGER);
DROP TABLE t2;
CREATE TABLE t2 ( name TEXT, n INTEGER);
DROP TABLE t3;
CREATE TABLE t3 ( name TEXT, n INTEGER);

INSERT INTO t1 VALUES ( 'aa', 11 );
INSERT INTO t2 VALUES ( 'aa', 12 );
INSERT INTO t2 VALUES ( 'bb', 22 );
INSERT INTO t3 VALUES ( 'aa', 13 );
INSERT INTO t3 VALUES ( 'cc', 33 );

SELECT * FROM t1 FULL JOIN t2 USING (name) FULL JOIN t3 USING (name); -- NG
ERROR: FULL JOIN is only supported with mergejoinable join conditions
--
Tatsuo Ishii

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2001-11-18 12:05:05 Re: OCTET_LENGTH is wrong
Previous Message Hannu Krosing 2001-11-18 07:24:45 Re: Multilingual application, ORDER BY w/ different