Re: I/O support for composite types

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: elein <elein(at)varlena(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: I/O support for composite types
Date: 2004-06-05 21:00:24
Message-ID: 916.1086469224@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> regression=# insert into bar values (row(row(1.1, 2.2), row(3.3, 4.4)));

BTW, I forgot to mention that the keyword ROW is optional as long as
you've got at least two items in the row expression, so the above can
be simplified to

regression=# insert into bar values (((1.1, 2.2), (3.3,4.4)));
INSERT 155011 1

Some other examples:

regression=# select (1,2)::complex;
ERROR: output of composite types not implemented yet
regression=# select cast ((1,2) as complex);
ERROR: output of composite types not implemented yet

Looking at these, it does seem like it would be natural to get back

complex
---------
(1,2)

so I'll now agree with you that the I/O syntax should use parens not
braces as the outer delimiters.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message elein 2004-06-05 21:34:56 Re: I/O support for composite types
Previous Message Marc G. Fournier 2004-06-05 20:58:22 Re: Official Freeze Date for 7.5: July 1st, 2004