Re: plpgsql bug OR future request: Assign fileds in composite subfiled. eg. table.compositefield.subfield := TRUE; - Mailing list pgsql-bugs

From Pavel Stehule
Subject Re: plpgsql bug OR future request: Assign fileds in composite subfiled. eg. table.compositefield.subfield := TRUE;
Date
Msg-id 162867790812100246w6bb60030x1c49b246bc3a415d@mail.gmail.com
Whole thread Raw
In response to plpgsql bug OR future request: Assign fileds in composite subfiled. eg. table.compositefield.subfield := TRUE;  ("Oleg Serov" <serovov@gmail.com>)
Responses Re: plpgsql bug OR future request: Assign fileds in composite subfiled. eg. table.compositefield.subfield := TRUE;
List pgsql-bugs
Hello

2008/12/10 Oleg Serov <serovov@gmail.com>:
> SQL:
> CREATE TABLE second_type (
>        flag BOOLEAN
> );
> CREATE TABLE main_type (
>        subtype second_type
> );
> CREATE OR REPLACE FUNCTION "bug_in_tabletypes" () RETURNS pg_catalog.void AS
> $body$
> DECLARE
>        row_main_table main_type%rowtype;
> BEGIN
>        row_main_table.subtype := NULL; -- all okey;



>        row_main_table.subtype.flag := FALSE; -- cannot set

try
  (row_main_table.subtype).flag := FALSE; -- cannot set

regards
Pavel Stehule

> END;
> $body$
> LANGUAGE 'plpgsql' VOLATILE CALLED ON NULL INPUT SECURITY INVOKER;
>
> Will produce error:
>
>
> ERROR:  syntax error at or near "row_main_table"
> LINE 1: row_main_table.subtype.flag := FALSE
>        ^
> QUERY:  row_main_table.subtype.flag := FALSE
> CONTEXT:  SQL statement in PL/PgSQL function "bug_in_tabletypes" near line
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>

pgsql-bugs by date:

Previous
From: "Pavel Stehule"
Date:
Subject: Re: Bug in plpgsql, when using NEW with composite field value.
Next
From: "Oleg Serov"
Date:
Subject: Re: plpgsql bug OR future request: Assign fileds in composite subfiled. eg. table.compositefield.subfield := TRUE;