feat(database): 为数据库输出DEBUG日志，以辅助解决ISSUE问题 #1080
Open
+177
−2
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
# Conflicts: # main.go
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
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.
目前有大量的ISSUE涉及到数据库问题，但我们难以进行复现，当前日志又没有任何输出，排查全靠猜。
基于此，我认为有必要将数据库的执行日志打印到DEBUG日志中并默认开启，从而针对代码进一步优化。
此处的代码打印机制来源于 曾经给小鸟添加 的提交。
当前打印机制： SQL执行前不打印。SQL执行后开始打印。SQL出错打印。
让我们看看到底是什么热闹吧！