On Fri, Mar 31, 2023 at 11:26 AM Tom Lane wrote:
> "David G. Johnston" writes:
> > On Fri, Mar 31, 2023 at 8:10 AM Zhang Mingli
> wrote:
> >> When I exec a sql SELECT INTO without columns or * by mistake, it
> succeeds:
>
> > Yes, a table may have zero columns by design.
>
> Yup, we've allowed
"David G. Johnston" writes:
> On Fri, Mar 31, 2023 at 8:10 AM Zhang Mingli wrote:
>> When I exec a sql SELECT INTO without columns or * by mistake, it succeeds:
> Yes, a table may have zero columns by design.
Yup, we've allowed that for some time now; see the compatibility comments
at the botto
On Fri, Mar 31, 2023 at 8:10 AM Zhang Mingli wrote:
> When I exec a sql SELECT INTO without columns or * by mistake, it succeeds:
>
>
Yes, a table may have zero columns by design.
David J.
Hi, hackers
When I exec a sql SELECT INTO without columns or * by mistake, it succeeds:
select * from t1;
a | b
---+---
1 | 2
2 | 3
3 | 4
(3 rows)
select into t2 from t1;
SELECT 3
\pset null '(null)'
Null display is "(null)".
select * from t2;
--
(3 rows)
It seems that t2 has empty rows
