QGIS » QGIS Application

I tested the PR. While it works fine in for normal PostgreSQL layers (not in transaction mode), it still fails when transaction mode is turned on.

The problem arises only if the two following project properties are activated:

• Automatically create transaction groups where possible
• Evaluate default values on provider side

Thanks for having a look at this specific "transaction mode" situation.

I am adding the create table statement of a concerned table that shows the issue:

CREATE TABLE ews.ews_geologie
(
    t_id bigint NOT NULL DEFAULT nextval('ews.t_ili2db_seq'::regclass),
    t_basket bigint NOT NULL DEFAULT 4,
    t_ili_tid uuid DEFAULT uuid_generate_v4(),
    zulaessigkeit bigint NOT NULL,
    gebietsnummer character varying(10) COLLATE pg_catalog."default",
    mutationsdatum date,
    geologie_intern text COLLATE pg_catalog."default",
    geologie_extern text COLLATE pg_catalog."default",
    bemerkungen_intern text COLLATE pg_catalog."default",
    bemerkungen_extern text COLLATE pg_catalog."default",
    geometrie geometry(Polygon,2056),
    CONSTRAINT ews_geologie_pkey PRIMARY KEY (t_id),
    CONSTRAINT ews_geologie_t_basket_fkey FOREIGN KEY (t_basket)
        REFERENCES ews.t_ili2db_basket (t_id) MATCH SIMPLE
        ON UPDATE NO ACTION
        ON DELETE NO ACTION
        DEFERRABLE INITIALLY DEFERRED,
    CONSTRAINT ews_geologie_zulaessigkeit_fkey FOREIGN KEY (zulaessigkeit)
        REFERENCES ews.zulaessigkeit_catalogue (t_id) MATCH SIMPLE
        ON UPDATE NO ACTION
        ON DELETE NO ACTION
        DEFERRABLE INITIALLY DEFERRED
)
WITH (
    OIDS = FALSE
)
TABLESPACE pg_default;

Note the bigint data type for the primary key column.