Re: plpgsql - DECLARE - cannot to use %TYPE or %ROWTYPE for composite types
От | Pavel Stehule |
---|---|
Тема | Re: plpgsql - DECLARE - cannot to use %TYPE or %ROWTYPE for composite types |
Дата | |
Msg-id | CAFj8pRB+ECM4hOhLD1ze-13uW=D9fhVi2ao5KLPvT_tYRU_ttg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: plpgsql - DECLARE - cannot to use %TYPE or %ROWTYPE for composite types (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: plpgsql - DECLARE - cannot to use %TYPE or %ROWTYPE for
composite types
|
Список | pgsql-hackers |
2016-03-16 16:50 GMT+01:00 Pavel Stehule <pavel.stehule@gmail.com>:
2016-03-16 16:46 GMT+01:00 Joe Conway <mail@joeconway.com>:On 03/15/2016 05:17 PM, Tom Lane wrote:
> In short, I think we should reject this implementation and instead try
> to implement the type operators we want in the core grammar's Typename
> production, from which plpgsql will pick it up automatically. That is
> going to require some other syntax than this. As I said, I'm not
> particularly pushing the function-like syntax I wrote upthread; but
> I want to see something that is capable of supporting all those features
> and can be extended later if we think of other type operators we want.
+1
Anyone want to argue against changing the status of this to Rejected or
at least Returned with feedback?I would to reduce this patch to fix row type issue. There is not any disagreement. I'll send reduced patch today.Any other functionality is not 9.6 topic.
I played with the reduced patch, and the benefit without all other things is negligible. It should be rejected.
Regards
Pavel
RegardsPavel
Joe
--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development
В списке pgsql-hackers по дате отправления: