Get rid of PostgreSQL trigger
Open
Nobody has claimed this yet.
enhancement
question
stale
- Dominant language
- Python
- Stars
- 4.4k
- Forks
- 438
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 15
Description
What happens in the bump_timestamp() trigger is hard to monitor and trace (e.g. does not appear on pg_activity).
We could investigate and see if we could move the behavior elegantly to Python code
Contributor 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.
Research direction
Start by locating the PostgreSQL bump_timestamp() trigger and tracing the related behavior in the Python code. Investigate how the behavior could be moved while remaining observable and traceable; done means the trigger is removed and equivalent behavior works through Python.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- backend, databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100