| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SELECT INTO deprecation |
| Date: | 2020-12-03 12:16:32 |
| Message-ID: | 8e05fc79-abca-dd3f-4d48-8aaae9525a8f@enterprisedb.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-12-03 00:54, Michael Paquier wrote:
> I got to wonder about the impact when migrating applications
> though. SELECT INTO has a different meaning in Oracle, but SQL server
> creates a new table like Postgres.
Interesting. This appears to be the case. SQL Server uses SELECT INTO
to create a table, and does not appear to have CREATE TABLE AS.
So maybe we should keep it, but adjust the documentation to point out
this use case.
[some snarky comment about AWS Babelfish here ... ;-) ]
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2020-12-03 12:22:35 | Re: Add session statistics to pg_stat_database |
| Previous Message | Peter Eisentraut | 2020-12-03 12:14:11 | Re: SELECT INTO deprecation |