mirror of
https://github.com/go-gitea/gitea
synced 2024-09-10 08:27:04 +02:00
Correct the database.LOG_SQL default value in config cheat sheet (#26997)
The default is false, fix the docs to reflect that. Fixes: #26989
This commit is contained in:
parent
dd6e8ab57b
commit
de68953bac
@ -446,7 +446,7 @@ The following configuration set `Content-Type: application/vnd.android.package-a
|
||||
- `SQLITE_JOURNAL_MODE`: **""**: Change journal mode for SQlite3. Can be used to enable [WAL mode](https://www.sqlite.org/wal.html) when high load causes write congestion. See [SQlite3 docs](https://www.sqlite.org/pragma.html#pragma_journal_mode) for possible values. Defaults to the default for the database file, often DELETE.
|
||||
- `ITERATE_BUFFER_SIZE`: **50**: Internal buffer size for iterating.
|
||||
- `PATH`: **data/gitea.db**: For SQLite3 only, the database file path.
|
||||
- `LOG_SQL`: **true**: Log the executed SQL.
|
||||
- `LOG_SQL`: **false**: Log the executed SQL.
|
||||
- `DB_RETRIES`: **10**: How many ORM init / DB connect attempts allowed.
|
||||
- `DB_RETRY_BACKOFF`: **3s**: time.Duration to wait before trying another ORM init / DB connect attempt, if failure occurred.
|
||||
- `MAX_OPEN_CONNS` **0**: Database maximum open connections - default is 0, meaning there is no limit.
|
||||
|
@ -436,7 +436,7 @@ menu:
|
||||
- `SQLITE_JOURNAL_MODE`:**""**:更改 SQlite3 的日志模式。可以用于在高负载导致写入拥塞时启用 [WAL 模式](https://www.sqlite.org/wal.html)。有关可能的值,请参阅 [SQlite3 文档](https://www.sqlite.org/pragma.html#pragma_journal_mode)。默认为数据库文件的默认值,通常为 DELETE。
|
||||
- `ITERATE_BUFFER_SIZE`:**50**:用于迭代的内部缓冲区大小。
|
||||
- `PATH`:**data/gitea.db**:仅适用于 SQLite3 的数据库文件路径。
|
||||
- `LOG_SQL`:**true**:记录已执行的 SQL。
|
||||
- `LOG_SQL`:**false**:记录已执行的 SQL。
|
||||
- `DB_RETRIES`:**10**:允许多少次 ORM 初始化 / DB 连接尝试。
|
||||
- `DB_RETRY_BACKOFF`:**3s**:如果发生故障,等待另一个 ORM 初始化 / DB 连接尝试的 time.Duration。
|
||||
- `MAX_OPEN_CONNS`:**0**:数据库最大打开连接数 - 默认为 0,表示没有限制。
|
||||
|
Loading…
Reference in New Issue
Block a user