Puzzled by ROW constructor behaviour? - Mailing list pgsql-general

From Eagna
Subject Puzzled by ROW constructor behaviour?
Date
Msg-id K1pl2RffHja6dj8lhYxL8J2FcbfaHau4O41XeWAsLLDWeQace2-l6GPIk49Ha4vh0FSewhOyUveTu96Rv2gvQDf77wElA0Vad0FSo7w_U6A=@protonmail.com
Whole thread Raw
Responses Re: Puzzled by ROW constructor behaviour?  (Steve Baldwin <steve.baldwin@gmail.com>)
Re: Puzzled by ROW constructor behaviour?  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general
Hi all,

I'm puzzled by some behaviour of the ROW constructor that I noticed when I was playing around.

From the documentation (https://www.postgresql.org/docs/current/sql-expressions.html#SQL-SYNTAX-ROW-CONSTRUCTORS), we
have

NUMBER 1

> SELECT ROW(1,2.5,'this is a test') = ROW(1, 3, 'not the same') AS test1;

result:

> test1
> f

This is fine.

and then

NUMBER 2

> SELECT ROW(1, 2.5, 'this is a test') = (VALUES (1, 2.5, 'this is a test')) AS test2;

result:

> test2
> t

OK - notice the equivalence of a ROW constructor and a VALUES clause.

So, then I create this table:

> CREATE TABLE test
> (
>  a INT NOT NULL,
>  b INT NOT NULL,
>  c TEXT NOT NULL
> );

and then tried:

NUMBER 3

> INSERT INTO test ((ROW (1, 2.4, 'test...')));

and I get:

> ERROR:  syntax error at or near "ROW"
> LINE 1: INSERT INTO test ((ROW (1, 2.4, 'test...')));


I tried various permutations of brackets and whatnot but nothing doing.


My question is that if a ROW constructor works for a VALUES clause in statement NUMBER 2, then why not NUMBER 3?


TIA and rgs,

E.





pgsql-general by date:

Previous
From: Brad White
Date:
Subject: Re: Upgrading to v12
Next
From: Steve Baldwin
Date:
Subject: Re: Puzzled by ROW constructor behaviour?