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

From Oleg Serov
Subject plpgsql bug OR future request: Assign fileds in composite subfiled. eg. table.compositefield.subfield := TRUE;
Date
Msg-id cec7c6df0812100219t5cc57ce3wba6c140fa288791a@mail.gmail.com
Whole thread Raw
Responses Re: plpgsql bug OR future request: Assign fileds in composite subfiled. eg. table.compositefield.subfield := TRUE;
List pgsql-bugs
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
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

pgsql-bugs by date:

Previous
From: "Oleg Serov"
Date:
Subject: Bug in plpgsql, when using NEW with composite field value.
Next
From: "Pavel Stehule"
Date:
Subject: Re: Bug in plpgsql, when using NEW with composite field value.