Обсуждение: [bug]? insert returning composite type fails

Поиск
Список
Период
Сортировка

[bug]? insert returning composite type fails

От
Lorusso Domenico
Дата:
Hello guys,
In my db (version 15) I've defined a composite type with some domains

CREATE DOMAIN my_feat.audit_record_jsonb_domain
    AS jsonb
    NOT NULL;

ALTER DOMAIN my_feat.audit_record_jsonb_domain OWNER TO postgres;

CREATE DOMAIN my_feat.boolean_true_domain
    AS boolean
    DEFAULT true
    NOT NULL;

ALTER DOMAIN my_feat.boolean_true_domain OWNER TO postgres;
CREATE TYPE my_feat.bitemporal_record AS
(
user_ts_range tstzrange,
db_ts_range tstzrange,
has_future_record timestamp with time zone,
audit_record my_feat.audit_record_jsonb_domain,
is_valid my_feat.boolean_true_domain
);

ALTER TYPE my_feat.bitemporal_record
    OWNER TO postgres;
So I've a table like that:
CREATE TABLE IF NOT EXISTS my_feat.try_bt_info
(
    id bigint NOT NULL GENERATED BY DEFAULT AS IDENTITY ( INCREMENT 1 START 1 MINVALUE 1 MAXVALUE 9223372036854775807 CACHE 1 ),
    bt_info my_feat.bitemporal_record,
    CONSTRAINT try_bt_info_pk PRIMARY KEY (id)
)

TABLESPACE pg_default;

ALTER TABLE IF EXISTS my_feat.try_bt_info
    OWNER to postgres;

When I try an insert asking to return bt_info I catch and error; here the example:

do $$
declare
_bt_info my_feat.bitemporal_record;
begin
insert into my_feat.try_bt_info (bt_info)
values (row(
tstzrange(now(),'infinity','[)')
, tstzrange(now(),'infinity','[)')
, null
, '{"user_id":"alpha"}'
, true)::my_feat.bitemporal_record
)
returning bt_info into _bt_info;

raise notice '%', _bt_info;
end;
$$;

Error:
ERROR: Too many commas.malformed range literal: "("[""2023-07-06 23:50:30.991122+02"",infinity)","[""2023-07-06 23:50:30.991122+02"",infinity)",,"{""user_id"": ""alpha""}",t)" ERROR: malformed range literal: "("[""2023-07-06 23:50:30.991122+02"",infinity)","[""2023-07-06 23:50:30.991122+02"",infinity)",,"{""user_id"": ""alpha""}",t)" SQL state: 22P02 
Detail: Too many commas.

It seems to be a bug, but maybe there is a workaround; any idea?

--
Domenico L.

per stupire mezz'ora basta un libro di storia,
io cercai di imparare la Treccani a memoria... [F.d.A.]

Re: [bug]? insert returning composite type fails

От
"David G. Johnston"
Дата:
On Thursday, July 6, 2023, Lorusso Domenico <domenico.l76@gmail.com> wrote:

returning bt_info into _bt_info;


I think it’s “returning (bt_info).* into _bt_info;”

David J.
 

Re: [bug]? insert returning composite type fails

От
Adrian Klaver
Дата:
On 7/6/23 14:52, Lorusso Domenico wrote:
> Hello guys,
> In my db (version 15) I've defined a composite type with some domains
> 
> CREATE DOMAIN my_feat.audit_record_jsonb_domain
>      AS jsonb
>      NOT NULL;
> 
> ALTER DOMAIN my_feat.audit_record_jsonb_domain OWNER TO postgres;
> 
> CREATE DOMAIN my_feat.boolean_true_domain
>      AS boolean
>      DEFAULT true
>      NOT NULL;
> 
> ALTER DOMAIN my_feat.boolean_true_domain OWNER TO postgres;
> CREATE TYPE my_feat.bitemporal_record AS
> (
> user_ts_range tstzrange,
> db_ts_range tstzrange,
> has_future_record timestamp with time zone,
> audit_record my_feat.audit_record_jsonb_domain,
> is_valid my_feat.boolean_true_domain
> );
> 
> ALTER TYPE my_feat.bitemporal_record
>      OWNER TO postgres;
> So I've a table like that:
> CREATE TABLE IF NOT EXISTS my_feat.try_bt_info
> (
>      id bigint NOT NULL GENERATED BY DEFAULT AS IDENTITY ( INCREMENT 1 
> START 1 MINVALUE 1 MAXVALUE 9223372036854775807 CACHE 1 ),
>      bt_info my_feat.bitemporal_record,
>      CONSTRAINT try_bt_info_pk PRIMARY KEY (id)
> )

Seems a long way around to arrive at:

CREATE TABLE IF NOT EXISTS my_feat.try_bt_info
(
id bigint NOT NULL GENERATED BY DEFAULT AS IDENTITY ( INCREMENT 1 START 
1 MINVALUE 1 MAXVALUE 9223372036854775807 CACHE 1 ) PRIMARY KEY,
user_ts_range tstzrange,
db_ts_range tstzrange,
has_future_record timestamp with time zone,
is_valid boolean NOT NULL 't'
);


> -- 
> Domenico L.
> 
> per stupire mezz'ora basta un libro di storia,
> io cercai di imparare la Treccani a memoria... [F.d.A.]

-- 
Adrian Klaver
adrian.klaver@aklaver.com

Re: [bug]? insert returning composite type fails

От
Lorusso Domenico
Дата:
Adrian come on 🤭
This is a reduced example.


The real usecase involves many tables with the bitemporal record 


However I solved using a record type ...

Il ven 7 lug 2023, 01:20 Adrian Klaver <adrian.klaver@aklaver.com> ha scritto:
On 7/6/23 14:52, Lorusso Domenico wrote:
> Hello guys,
> In my db (version 15) I've defined a composite type with some domains
>
> CREATE DOMAIN my_feat.audit_record_jsonb_domain
>      AS jsonb
>      NOT NULL;
>
> ALTER DOMAIN my_feat.audit_record_jsonb_domain OWNER TO postgres;
>
> CREATE DOMAIN my_feat.boolean_true_domain
>      AS boolean
>      DEFAULT true
>      NOT NULL;
>
> ALTER DOMAIN my_feat.boolean_true_domain OWNER TO postgres;
> CREATE TYPE my_feat.bitemporal_record AS
> (
> user_ts_range tstzrange,
> db_ts_range tstzrange,
> has_future_record timestamp with time zone,
> audit_record my_feat.audit_record_jsonb_domain,
> is_valid my_feat.boolean_true_domain
> );
>
> ALTER TYPE my_feat.bitemporal_record
>      OWNER TO postgres;
> So I've a table like that:
> CREATE TABLE IF NOT EXISTS my_feat.try_bt_info
> (
>      id bigint NOT NULL GENERATED BY DEFAULT AS IDENTITY ( INCREMENT 1
> START 1 MINVALUE 1 MAXVALUE 9223372036854775807 CACHE 1 ),
>      bt_info my_feat.bitemporal_record,
>      CONSTRAINT try_bt_info_pk PRIMARY KEY (id)
> )

Seems a long way around to arrive at:

CREATE TABLE IF NOT EXISTS my_feat.try_bt_info
(
id bigint NOT NULL GENERATED BY DEFAULT AS IDENTITY ( INCREMENT 1 START
1 MINVALUE 1 MAXVALUE 9223372036854775807 CACHE 1 ) PRIMARY KEY,
user_ts_range tstzrange,
db_ts_range tstzrange,
has_future_record timestamp with time zone,
is_valid boolean NOT NULL 't'
);


> --
> Domenico L.
>
> per stupire mezz'ora basta un libro di storia,
> io cercai di imparare la Treccani a memoria... [F.d.A.]

--
Adrian Klaver
adrian.klaver@aklaver.com