Repository navigation
Commit e1634b3
authored
Define
## Motivation for the change, related issues
The SQLite integration is adopting **`DB_PATH`** as its primary database
path setting. Playground currently supplies only `DB_DIR` and `DB_FILE`
when `dataSqlPath` is set.
## Implementation details
Define `DB_PATH` from `dataSqlPath`, keeping the matching legacy
constants for older SQLite plugin versions.
## Testing Instructions (or ideally a Blueprint)
Boot with `dataSqlPath` set to a custom SQLite file and confirm
WordPress opens that file. Verified with SQLite integration v2.1.16,
bundled trunk, and the build from PR
[#512](WordPress/sqlite-database-integration#512).
Related:
WordPress/sqlite-database-integration#512.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **New Features**
* WordPress boot now uses the provided SQL data path to configure its
database location, improving support for custom database setups.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->DB_PATH for explicit SQLite database paths (#4374)1 parent 8750c89 commit e1634b3
1 file changed
Lines changed: 3 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
263 | 263 | | |
264 | 264 | | |
265 | 265 | | |
| 266 | + | |
| 267 | + | |
| 268 | + | |
266 | 269 | | |
267 | 270 | | |
268 | 271 | | |
| |||
0 commit comments