d1cb590c78
- 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 866229bc323619bc8686bad99951f95d5d46fe19) (cherry picked from commit 96dd3e87cf5f75ac33bfad647e44852667c307d0) (cherry picked from commit e165510317b3fe3be4fe49ad3ff0a055e7a92124) (cherry picked from commit 1638e2b3f56a508dbf218207bf0c3c4d16493255) |
||
|---|---|---|
| .. | ||
| install | ||
| paginator | ||
| collation.go | ||
| common.go | ||
| consistency.go | ||
| context.go | ||
| context_committer_test.go | ||
| context_test.go | ||
| convert.go | ||
| engine.go | ||
| engine_test.go | ||
| error.go | ||
| index.go | ||
| index_test.go | ||
| iterate.go | ||
| iterate_test.go | ||
| list.go | ||
| list_test.go | ||
| log.go | ||
| main_test.go | ||
| name.go | ||
| search.go | ||
| sequence.go | ||
| sql_postgres_with_schema.go | ||