ext/pgsql: introducing pg_result_verbose_error(). #18192
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
unlike pg_set_error_context_visibility()/pg_set_error_verbosity(), it is affecting only a particular PgSql\Result instance rather than the whole PgSql\Connection, e.g. debugging a problematic SQL request. Available since postgresql 14.
|
is irrelevant, works only with non freed but problematic pgresult.. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
unlike pg_set_error_context_visibility()/pg_set_error_verbosity(), it is affecting only a particular PgSql\Result instance rather than the whole PgSql\Connection, e.g. debugging a problematic SQL request. Available since postgresql 14.