Skip to content

Commit 83deeb4

Browse files
committed
Changing release note wording, explicitly mentioning
we don't support PRAGMA optimize(-1).
1 parent 367b34d commit 83deeb4

File tree

3 files changed

+9
-4
lines changed

3 files changed

+9
-4
lines changed

src/content/partials/d1/use-pragma-statements.mdx

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -420,6 +420,10 @@ When `PRAGMA optimize` runs `ANALYZE`, it sets a limit to ensure the command doe
420420

421421
We recommend running this command after making any changes to the schema (for example, after [creating an index](/d1/best-practices/use-indexes/)).
422422

423-
{/* Alternatively, to see all optimizations that would have been performed without actually executing them, run `PRAGMA optimize(-1)`. */}
423+
:::note
424+
Currently, D1 does not support `PRAGMA optimize(-1)`.
425+
426+
`PRAGMA optimize(-1)` is a command which displays all optimizations that would have been performed without actually executing them.
427+
:::
424428

425429
Refer to [SQLite PRAGMA optimize documentation](https://www.sqlite.org/pragma.html#pragma_optimize) for more information on how `PRAGMA optimize` optimizes a database.

src/content/release-notes/d1.yaml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,6 @@ entries:
1010
description: |-
1111
D1 now supports `PRAGMA optimize` command, which can improve database query performance. It is recommended to run this command after a schema change (for example, after creating an index). Refer to [`PRAGMA optimize`](/d1/sql-api/sql-statements/#pragma-optimize) for more information.
1212
13-
Cloudflare recommends running this command after a schema change (for example, after creating an index).
14-
1513
- publish_date: "2025-02-04"
1614
title: Fixed bug with D1 read-only access via UI and /query REST API.
1715
description: |-

src/content/release-notes/durable-objects.yaml

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,14 +7,17 @@ productAreaLink: /workers/platform/changelog/platform/
77
entries:
88
- publish_date: "2025-02-19"
99
description: |-
10-
SQLite-backed Durable Objects now supports `PRAGMA optimize` command. Refer to [`PRAGMA optimize`](/d1/sql-api/sql-statements#pragma-optimize) for more information.
10+
SQLite-backed Durable Objects now support `PRAGMA optimize` command, which can improve database query performance. It is recommended to run this command after a schema change (for example, after creating an index). Refer to [`PRAGMA optimize`](/d1/sql-api/sql-statements/#pragma-optimize) for more information.
11+
1112
- publish_date: "2025-02-11"
1213
description: |-
1314
When Durable Objects generate an "internal error" exception in response to certain failures, the exception message may provide a reference ID that customers can include in support communication for easier error identification. For example, an exception with the new message might look like: `internal error; reference = 0123456789abcdefghijklmn`.
15+
1416
- publish_date: "2024-10-07"
1517
title: Alarms re-enabled in (beta) SQLite-backed Durable Object classes
1618
description: |-
1719
The issue identified with [alarms](/durable-objects/api/alarms/) in [beta Durable Object classes with a SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage/#sqlite-storage-backend) has been resolved and alarms have been re-enabled.
20+
1821
- publish_date: "2024-09-27"
1922
title: Alarms disabled in (beta) SQLite-backed Durable Object classes
2023
description: |-

0 commit comments

Comments
 (0)