fix(templates): added missing CLOUDFLARE_ENV when optimizing database #14064
Conversation
This file contains hidden or 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
paulpopus approved these changes Oct 3, 2025
Contributor
| 🚀 This is included in version v3.59.0 |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
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.
What?
Adds the missing
$CLOUDFLARE_ENVenv parameter when optimizing the D1 database after deploy.Switched from
-eto--envas-edoesn't handle it very well when$CLOUDFLARE_ENVis empty.Why?
Running "PRAGMA optimize" tells D1/SQLite to refresh its statistics for the query planner. This is crucial whenever an index is added or removed.
How?
By adding the "--env" parameter to the
wrangler d1 executecommand