From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Quan Zongliang <quanzongliang(at)yeah(dot)net> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PL/pgSQL: Incomplete item Allow handling of %TYPE arrays, e.g. tab.col%TYPE[] |
Date: | 2023-11-24 05:00:42 |
Message-ID: | CAFj8pRBFePm8bQd_CJbyhf4f36iqZqO0x-PrFJLaZ=FmU+SUbA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
pá 24. 11. 2023 v 2:12 odesílatel Quan Zongliang <quanzongliang(at)yeah(dot)net>
napsal:
>
>
> On 2023/11/24 03:39, Pavel Stehule wrote:
>
> >
> > I modified the documentation a little bit - we don't need to extra
> > propose SQL array syntax, I think.
> > I rewrote regress tests - we don't need to test unsupported
> > functionality (related to RECORD).
> >
> > - all tests passed
> >
> I wrote two examples of errors:
> user_id users.user_id%ROWTYPE[];
> user_id users.user_id%ROWTYPE ARRAY[4][3];
>
there were more issues in this part - the name "user_id" is a bad name for
a composite variable. I renamed it.
+ I wrote a test related to usage type without array support.
Now, I think so this simple patch is ready for committers
Regards
Pavel
> Fixed.
>
> > Regards
> >
> > Pavel
> >
> >
> > >
> > > Regards
> > >
> > > Pavel
> >
Attachment | Content-Type | Size |
---|---|---|
v20231124-0001-support-of-syntax-type-and-rowtype.patch | text/x-patch | 10.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Alena Rybakina | 2023-11-24 05:05:14 | Re: POC, WIP: OR-clause support for indexes |
Previous Message | Dilip Kumar | 2023-11-24 04:47:54 | Re: SLRU optimization - configurable buffer pool and partitioning the SLRU lock |