Gusted 1638e2b3f5 [GITEA] Log SQL queries when the database return error ... - When the database returns an error about the SQL query, the error is logged but not the SQL query and arguments, which is just as valuable as the vague deeply hidden documented error that the database returns. It's possible to log the SQL query by logging **all** SQL queries. For bigger instances such as Codeberg, this is not a viable option. - Adds a new hook, enabled by default, to log SQL queries with their arguments and the error returned by the database when the database returns an error. - This likely needs some fine tuning in the future to decide when to enable this, as the error is already logged and if people have the `[database].LOG_SQL` option enabled, the SQL would be logged twice. But given that it's an rare occurence for SQL queries to error, it's fine to leave that as-is. - Ref: https://codeberg.org/forgejo/forgejo/issues/1998 (cherry picked from commit 866229bc32) (cherry picked from commit 96dd3e87cf) (cherry picked from commit e165510317)		2024-01-28 10:58:28 +01:00
..
actions
activities
admin
asymkey
auth
avatars
db
dbfs
fixtures
forgejo/semver
forgejo_migrations
git
issues
migrations
organization
packages
perm
project
pull
repo
secret
shared/types
system
unit
unittest
user
webhook
error.go
fixture_generation.go
fixture_test.go
main_test.go
org.go
org_team.go
org_team_test.go
org_test.go
repo.go
repo_test.go
repo_transfer.go
repo_transfer_test.go