Subject: Re: SELECT INTO deprecation
To: Tom Lane <tgl@sss.pgh.pa.us>
References: <96dc0df3-e13a-a85d-d045-d6e2c85218da@enterprisedb.com>
 <20201202175836.GX16415@tamriel.snowman.net>
 <1672926.1606941346@sss.pgh.pa.us> <X8gpP9GL7R5AsF3E@paquier.xyz>
 <8e05fc79-abca-dd3f-4d48-8aaae9525a8f@enterprisedb.com>
 <1723856.1607009655@sss.pgh.pa.us>
Cc: Michael Paquier <michael@paquier.xyz>, Stephen Frost
 <sfrost@snowman.net>, pgsql-hackers <pgsql-hackers@postgresql.org>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Organization: EnterpriseDB
Message-ID: <a71c0215-3ab1-abab-babe-2778b17aa1d7@enterprisedb.com>
Date: Thu, 3 Dec 2020 20:26:59 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0)
 Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <1723856.1607009655@sss.pgh.pa.us>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 2020-12-03 16:34, Tom Lane wrote:
> As I recall, a whole lot of the pain we have with INTO has to do
> with the semantics we've chosen for INTO in a set-operation nest.
> We think you can write something like
> 
>     SELECT ... INTO foo FROM ... UNION SELECT ... FROM ...
> 
> but we insist on the INTO being in the first component SELECT.
> I'd like to know exactly how much of that messiness is shared
> by SQL Server.

On sqlfiddle.com, this works:

select a into t3 from t1 union select a from t2;

but this gets an error:

select a from t1 union select a into t4 from t2;

SELECT INTO must be the first query in a statement containing a UNION, 
INTERSECT or EXCEPT operator.