A column with a trigger is not updated when a data change is made through the Data Output section
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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
- 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
);
- 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();
- Do an
INSERTquery :
INSERT INTO mytable VALUES (DEFAULT, 'Something', current_timestamp);
- Do a
SELECTquery :
SELECT * FROM mytable;
🟢 Seen & expected behavior :
- the inserted row can be seen in the "Data Output" section
- the
datecolumn has been correctly filled (by the trigger) and is correctly displayed
-
Change the value of one of the columns (but not the
dateone) through the "Data Output" section -
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
- Do a
SELECTquery
SELECT * FROM mytable;
🟢 Seen & expected behavior :
- the edited row can be seen in the "Data Output" section
- the
datecolumn is now correctly displayed (with its updated value)
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).
- Dominant language
- Python
- Stars
- 3.9k
- Forks
- 922
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 33
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pgadmin-org/pgadmin4
-
Invalid syntax in sshtunnelPossibly taken A pull request linked to this issue is open or already merged. OpenBug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
pgadmin-org/pgadmin4#10797 ·
Maintainers usually reply within 2 days
-
Feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pgadmin-org/pgadmin4#10426 · 3 comments · 1 reaction ·
Maintainers usually reply within 2 days
-
Bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
pgadmin-org/pgadmin4#10796 · 1 comment ·
Maintainers usually reply within 2 days
-
Schema Diff does not detect foreign keys that reference a different schemaPossibly taken @dpage claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 57/100
pgadmin-org/pgadmin4#10786 · 1 assignee ·
Maintainers usually reply within 2 days
-
Bug
Difficulty 4/5 3-5 days Newbie friendliness 55/100
pgadmin-org/pgadmin4#10783 ·
Maintainers usually reply within 2 days
All issues in pgadmin-org/pgadmin4
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mohanraj00/entelos#200 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
sweep
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
bketelsen/truenas-mcp#77 ·
Maintainers usually reply within 1 day
-
Console writes URL credentials to the local log, though AGENTS.md says secrets never reach diskOpen
Difficulty 1/5 Under an hour Newbie friendliness 86/100
sandbox-quantum/switch#2163 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
openedx/xblock-lti-consumer#765 ·
Maintainers usually reply within 1 day