Daniel Gustafsson writes:
> Thanks, I'll await pushing and backpatching if Tom who committed it has
> insights into whether it was missed or if it indeed serves a purpose.
Hey, I just pushed that for somebody else, I don't claim authorship ;-)
It seems clear that the example intends to show a
> On 26 Oct 2023, at 12:31, Maxim Yablokov wrote:
>
> I believe that the attached patch should fix this problem. Please have a look.
Thanks, I'll await pushing and backpatching if Tom who committed it has
insights into whether it was missed or if it indeed serves a purpose. If not I
think it
I believe that the attached patch should fix this problem. Please have a
look.
26.10.2023 12:29, Daniel Gustafsson пишет:
On 26 Oct 2023, at 09:33, Maxim Yablokov wrote:
Example 43.6 on the pagehttps://www.postgresql.org/docs/16/plpgsql-trigger.html
has two tables called main. But it seems
Yeah, sure thing! Thanks! I'll send a patch soon.
26.10.2023 12:29, Daniel Gustafsson пишет:
On 26 Oct 2023, at 09:33, Maxim Yablokov wrote:
Example 43.6 on the pagehttps://www.postgresql.org/docs/16/plpgsql-trigger.html
has two tables called main. But it seems that the table time_dimension
> On 26 Oct 2023, at 09:33, Maxim Yablokov wrote:
> Example 43.6 on the page
> https://www.postgresql.org/docs/16/plpgsql-trigger.html has two tables called
> main. But it seems that the table time_dimension is not used any further,
> it's a bit strange for one of main tables of the example.
Hello!
Example 43.6 on the page
https://www.postgresql.org/docs/16/plpgsql-trigger.html has two tables
called main. But it seems that the table *time_dimension* is not used
any further, it's a bit strange for one of main tables of the example.
Am I missing something, or should this example
