postgres version
10, but I have loaded the database in older versions of Postgresql and the problem remain.
your table structure
CREATE TABLE public.forniture_ee
(
id_cliente integer NOT NULL,
pod character varying(14) NOT NULL,
id_fornitore integer NOT NULL,
mese integer NOT NULL,
anno integer NOT NULL,
imponibile_fornitura double precision NOT NULL,
lettura character varying NOT NULL,
f1 double precision NOT NULL,
f2 double precision NOT NULL,
f3 double precision NOT NULL,
picco double precision NOT NULL,
fuori_picco double precision NOT NULL,
mono double precision NOT NULL,
perdite_di_rete double precision NOT NULL,
potenza_max double precision NOT NULL,
potenza_disponibile double precision NOT NULL,
costo_potenza_max double precision NOT NULL,
energia_reattiva double precision NOT NULL,
imponibile_energia double precision NOT NULL,
report_inviato boolean,
energia_e_perdite double precision NOT NULL,
CONSTRAINT forniture_ee_pkey PRIMARY KEY (id_cliente, pod, id_fornitore, mese, anno, imponibile_fornitura, lettura, f1, f2, f3, picco, fuori_picco, mono, perdite_di_rete, potenza_max, potenza_disponibile, costo_potenza_max, energia_reattiva, imponibile_energia, energia_e_perdite),
CONSTRAINT forniture_ee_id_cliente_fkey FOREIGN KEY (id_cliente)
REFERENCES public.anagrafica_clienti (id_cliente) MATCH SIMPLE
ON UPDATE NO ACTION ON DELETE NO ACTION,
CONSTRAINT forniture_ee_id_fornitore_fkey FOREIGN KEY (id_fornitore)
REFERENCES public.anagrafica_fornitori (id_fornitore) MATCH SIMPLE
ON UPDATE NO ACTION ON DELETE NO ACTION,
CONSTRAINT forniture_ee_pod_fkey FOREIGN KEY (pod)
REFERENCES public.pod (pod) MATCH SIMPLE
ON UPDATE NO ACTION ON DELETE NO ACTION
)
WITH (
OIDS=FALSE
);
ALTER TABLE public.forniture_ee
OWNER TO postgres;
(
id_cliente integer NOT NULL,
pod character varying(14) NOT NULL,
id_fornitore integer NOT NULL,
mese integer NOT NULL,
anno integer NOT NULL,
imponibile_fornitura double precision NOT NULL,
lettura character varying NOT NULL,
f1 double precision NOT NULL,
f2 double precision NOT NULL,
f3 double precision NOT NULL,
picco double precision NOT NULL,
fuori_picco double precision NOT NULL,
mono double precision NOT NULL,
perdite_di_rete double precision NOT NULL,
potenza_max double precision NOT NULL,
potenza_disponibile double precision NOT NULL,
costo_potenza_max double precision NOT NULL,
energia_reattiva double precision NOT NULL,
imponibile_energia double precision NOT NULL,
report_inviato boolean,
energia_e_perdite double precision NOT NULL,
CONSTRAINT forniture_ee_pkey PRIMARY KEY (id_cliente, pod, id_fornitore, mese, anno, imponibile_fornitura, lettura, f1, f2, f3, picco, fuori_picco, mono, perdite_di_rete, potenza_max, potenza_disponibile, costo_potenza_max, energia_reattiva, imponibile_energia, energia_e_perdite),
CONSTRAINT forniture_ee_id_cliente_fkey FOREIGN KEY (id_cliente)
REFERENCES public.anagrafica_clienti (id_cliente) MATCH SIMPLE
ON UPDATE NO ACTION ON DELETE NO ACTION,
CONSTRAINT forniture_ee_id_fornitore_fkey FOREIGN KEY (id_fornitore)
REFERENCES public.anagrafica_fornitori (id_fornitore) MATCH SIMPLE
ON UPDATE NO ACTION ON DELETE NO ACTION,
CONSTRAINT forniture_ee_pod_fkey FOREIGN KEY (pod)
REFERENCES public.pod (pod) MATCH SIMPLE
ON UPDATE NO ACTION ON DELETE NO ACTION
)
WITH (
OIDS=FALSE
);
ALTER TABLE public.forniture_ee
OWNER TO postgres;
how you are updating the records
Also by opening the table on PGADMIN.
if the problem is reproducible directly from the postgres prompt
I don't have try.
how you are fetching results after the update
By refreshing the table, in PgAdmin.
anything else to make the situation more clear (like errors in the logfile, or anything else you think is relevant)
No errors in the GUI, no errors in PgAdmin.log
--
Marco Fochesato