hi team, should monetdb throw an informative error when SELECT * gets used with UNION?  monetdb and postgres both allow users to make the mistake below.  from my perspective it should simply fail instead of mis-matching silently.  thanks


---------- Forwarded message ----------
From: <bugzilla-daemon@monetdb.org>
Date: Wed, Mar 23, 2016 at 10:42 AM
Subject: [Bug 3960] SELECT * with UNION ALL does not check column order
To: ajdamico@gmail.com


https://www.monetdb.org/bugzilla/show_bug.cgi?id=3960

Niels Nes <niels@cwi.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #4 from Niels Nes <niels@cwi.nl> ---
postgres=#
postgres=# CREATE TABLE x ( a integer , b integer );
CREATE TABLE
postgres=# CREATE TABLE y ( b integer , a integer);
CREATE TABLE
postgres=# INSERT INTO x VALUES ( 1 , 2 ) ;
INSERT 0 1
postgres=# INSERT INTO y VALUES ( 3 , 4 ) ;
INSERT 0 1
postgres=# select * from x;
 a | b
---+---
 1 | 2
(1 row)

postgres=# select * from y;
 b | a
---+---
 3 | 4
(1 row)

postgres=# CREATE TABLE z AS ( SELECT * FROM x ) UNION ALL ( SELECT * FROM y )
WITH DATA;
SELECT 2
postgres=# SELECT * FROM z;
 a | b
---+---
 1 | 2
 3 | 4
(2 rows)


ie what we do is normal behaviour....

--
You are receiving this mail because:
You are on the CC list for the bug.
You reported the bug.