Re: Automatically parsing in-line composite types

From: Mitar <mmitar(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, f(dot)venchiarutti(at)ocado(dot)com, Dave Cramer <pg(at)fastcrypt(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Automatically parsing in-line composite types
Date: 2019-10-31 16:48:43
Message-ID: CAKLmikOSe4t=KyVFQNpJqGCHfBi_WLcRTSgstUVmskZA5M36pg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi!

On Thu, Oct 31, 2019 at 7:59 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> tl;dr: there are a lot more worms in this can than you might guess.

But with all those issues, how do people then use compound types in
practice at all? Just at the top-level and have custom code to parse
them out for every query they are making?

Mitar

--
http://mitar.tnode.com/
https://twitter.com/mitar_m

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Daulat Ram 2019-10-31 17:29:34 Barman
Previous Message Tom Lane 2019-10-31 14:59:50 Re: Automatically parsing in-line composite types