[Bug] Constraint trigger incorrectly reported as non-deferrable/deferred
- Dominant language
- Python
- Stars
- 486
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
To reproduce:
1. Create a table and give it a `DEFERRABLE INITIALLY DEFERRED` constraint trigger.
2. Verify that the trigger is created successfully, with `tgdeferrable` and `tginitdeferred` both set to true in `pg_catalog.pg_trigger`.
3. View the table's definition in Postico's DDL view; observe that the DDL for the trigger trigger shows as `NOT DEFERRABLE`.
Postico Version 2.1.2 (9702)
Contributor guide
No contributing guide indexed for this repository
Research direction
No implementation file or test is named in the report. Start by reproducing the issue with a DEFERRABLE INITIALLY DEFERRED constraint trigger and inspect the DDL view output against pg_catalog.pg_trigger; done means the generated DDL preserves both deferrability settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100