Remove connection logs to avoid recursive stack when using the database as the log store #9
Conversation
This file contains 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
Similar to pixelvide#8, this is for the PostgresConnector. This entirely removes the log line. Some frameworks and plugins use the database as their log store, so having a log statement in the connector code can cause a recursive stack.
It is common for frameworks to use databases as log stores. Having logging within the database connection code can lead to recursive stack situations.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change removes log statements from both the PostgresConnector.php and MySqlConnector.php. Some frameworks and plugins use the database as their log store, so having a log statement in the connector code can cause a recursive stack.
Resolves #10