A column with a trigger is not updated when a data change is made through the Data Output section

Offen
#9,598 5 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Veraltet
Tech-Stack
postgresql, python
Bereich
database, frontend

Rechercherichtung

Reproduce the issue in pgAdmin's Data Output section using the supplied PostgreSQL table, trigger, and INSERT/UPDATE steps. Start with the Save Data Changes flow and compare the edited row with the database result after the trigger runs. Done means the Data Output section refreshes the trigger-updated date column immediately after saving, without requiring a separate SELECT.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Feature

Hi !

1. What

I think that a column with a trigger is not updated in the Data Output section after a Data Change has been made on another column.

Here are my pgAdmin infos :

  • Version : 9.11
  • Application Mode : Desktop
  • Commit : dc801e362ebde7fe59ecf77eaaab740fe7452cc5 2025-12-08
  • Python Version : 3.14.1
  • Browser : Chrome 143.0.0.0
  • Operating System : Alpine Linux v3.23, Linux-6.12.10-76061203-generic-x86_64-with-musl1

2. How

  1. Create a new table with a few columns, including one date column
CREATE TABLE mytable (
  id SERIAL PRIMARY KEY,
  value TEXT,
  date TIMESTAMP WITH TIME ZONE
);
  1. Add a trigger to this table :
CREATE OR REPLACE FUNCTION public.myfunction()
RETURNS TRIGGER AS $$
  BEGIN
    NEW.date = NOW();
    RETURN NEW;
  END;
$$ language 'plpgsql';

CREATE OR REPLACE TRIGGER mytrigger
BEFORE INSERT OR UPDATE ON mytable
FOR EACH ROW EXECUTE FUNCTION myfunction();
  1. Do an INSERT query :
INSERT INTO mytable VALUES (DEFAULT, 'Something', current_timestamp);
  1. Do a SELECT query :
SELECT * FROM mytable;

🟢 Seen & expected behavior :

  • the inserted row can be seen in the "Data Output" section
  • the date column has been correctly filled (by the trigger) and is correctly displayed
Image
  1. Change the value of one of the columns (but not the date one) through the "Data Output" section

  2. Press the "Save Data Changes" button

🔴 Seen behavior : only the edited column is up to date in the "Data Output" section
Expected behavior : the date column should be up to date as well

Image
  1. Do a SELECT query
SELECT * FROM mytable;

🟢 Seen & expected behavior :

  • the edited row can be seen in the "Data Output" section
  • the date column is now correctly displayed (with its updated value)
Image

3. Why

It seems that, after a successful "Data Change", pgAdmin doesn't get the last known value of the row (or of the other attributes of the row). It only updates the modified cell(s).

Vorherrschende Sprache
Python
Sterne
3.9k
Forks
922
Ø Merge
2 T. 3 Std.
Gemergte PRs (30 T.)
33

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus pgadmin-org/pgadmin4

Alle Issues in pgadmin-org/pgadmin4

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.