Support exit on script errors for programatic connects.
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
Research direction
Start by locating the shell script that establishes the psql connection and inspect how its arguments are passed to the session. Add the requested --exit-on-err behavior without changing the default user-shell behavior, then verify both connection modes and error handling.
Written by the indexing model from the issue text.
Description
When connecting to, for example, load the schema, we want the process to exit on errors. This can be done with:
psql -v ON_ERROR_STOP=1
On the other hand, when connecting for a user shell, we don't want that. So, the script should support a --exit-on-err flag, which would add the session variable as above.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
adobe-fonts/source-serif#152 ·
-
area:ansible source:reader type:content-error
Difficulty 1/5 Under an hour Newbie friendliness 86/100
stephrobert/blog-roadmap#42 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nolabs-ai/nono-packs#44 ·
Maintainers usually reply within 1 day