From: | Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com> |
---|---|
To: | aljosa(at)ekomunala(dot)com |
Cc: | pgadmin-support(at)lists(dot)postgresql(dot)org |
Subject: | Re: Issue with Saving Data Changes in Latest pgAdmin Version |
Date: | 2025-02-13 11:04:00 |
Message-ID: | CANxoLDeznXcCVrYdNG2y9QaM7coWdi+WimMZFkpauCVqS+FpBw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hi Aljoša,
I am not able to reproduce the issue. If I understand correctly following
is my table DDL:
CREATE TABLE public.test_serial
(
id serial NOT NULL,
name character varying,
PRIMARY KEY (id)
);
When I add a few rows via the GUI I can Save it with the proper sequence
value.
[image: Screenshot 2025-02-13 at 4.27.20 PM.png].
[image: Screenshot 2025-02-13 at 4.27.30 PM.png]
Please provide the exact reproduction steps.
On Thu, Feb 13, 2025 at 4:17 PM <aljosa(at)ekomunala(dot)com> wrote:
> Dear pgAdmin Support Team,
>
> Since installing the latest version of pgAdmin, I’ve encountered an issue
> when adding a new row via the GUI. The "Save Data Changes" function no
> longer works due to a primary key field. This field has a default value,
> and I’m not entering anything manually into it.
>
> In previous versions, pgAdmin automatically handled the next value from
> the sequence, but this no longer seems to be the case.
>
> Thank you in advance for your assistance.
>
>
>
>
>
> Kind regards,
>
>
>
> Aljoša Abrahamsberg
>
> *Studio GIS d.o.o.*Gornje Lepovče 22, SI-1310 Ribnica
> Tel: +386 (0)30 709 919
> aljosa(at)ekomunala(dot)com
> www.ekomunala.com
>
>
>
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Fredy Hurtado | 2025-02-14 11:37:50 | export statistics reports |
Previous Message | aljosa | 2025-02-12 17:16:51 | Issue with Saving Data Changes in Latest pgAdmin Version |