PostgreSQL: only raised error is shown
See original GitHub issueIn postgresql connection there is not shown notices or warning. I have procedure which raises many concrete warnings if whatever is bad. At the end of procedure there is raised error in case when whatever was bad. But DBeaver shows only this error and not shows these warning/notices despite the fact, that I added following line to the first line of SQL editor with procedure:
SET client_min_messages TO warning;
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Documentation: 15: 43.9. Errors and Messages - PostgreSQL
EXCEPTION raises an error (which normally aborts the current transaction); the other levels only generate messages of different priority levels.
Read more >How to raise errors and report messages within stored ...
This article discusses the RAISE command for reporting errors, warnings, and other report messages within stored procedures and functions in ...
Read more >Raising error in postgreSQL - plpgsql - Stack Overflow
Raising error in postgreSQL ... Giving error: syntax error at or near "cannot" LINE 5: RAISE EXCEPTION 'cannot have a negative ... I...
Read more >PostgreSQL RAISE EXCEPTION - eduCBA
PostgreSQL raises an exception is used to raise the statement for reporting the warnings, errors and other type of reported message within a...
Read more >postgresql - Generate an exception with a Context
Call another function that raises the error (warning, notice, ..) for you. Optionally with custom message and CONTEXT . Works with PostgreSQL 9.0...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You should use out view tab in SQL editor:
The view you opened in the bottom is legacy and it doesn’t work. We’ll remove it completely in the next version. Thanks for noticing.
Currently using version 5.1.3.
It seems that the issue is back. No notice is displayed in DBeaver’s output tab!