Skip to content

Commit 8ce2f84

Browse files
Oxyjunranbel
andauthored
Apply suggestions from code review
Co-authored-by: ranbel <[email protected]>
1 parent 711a5fb commit 8ce2f84

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

src/content/docs/d1/best-practices/import-export-data.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -149,7 +149,7 @@ npx wrangler d1 export <database_name> --remote --table=<table_name> --output=./
149149

150150
- Export is not supported for virtual tables, including databases with virtual tables. D1 supports virtual tables for full-text search using SQLite's [FTS5 module](https://www.sqlite.org/fts5.html). As a workaround, delete any virtual tables, export, and then recreate virtual tables.
151151
- A running export will block other database requests.
152-
- Any numeric value in a column is affected by the JavaScript's 52-bit precision for numbers. If you store a very large number (in `int64`), then retrieve the same value, the returned value may be less precise than your original number.
152+
- Any numeric value in a column is affected by JavaScript's 52-bit precision for numbers. If you store a very large number (in `int64`), then retrieve the same value, the returned value may be less precise than your original number.
153153

154154
## Troubleshooting
155155

src/content/docs/d1/worker-api/return-object.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -101,5 +101,5 @@ return Response.json(returnValue);
101101
```
102102

103103
:::note[Storing large numbers]
104-
Any numeric value in a column is affected by the JavaScript's 52-bit precision for numbers. If you store a very large number (in `int64`), then retrieve the same value, the returned value may be less precise than your original number.
104+
Any numeric value in a column is affected by JavaScript's 52-bit precision for numbers. If you store a very large number (in `int64`), then retrieve the same value, the returned value may be less precise than your original number.
105105
:::

src/content/docs/durable-objects/api/storage-api.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -149,7 +149,7 @@ console.log(cursor.toArray()); // prints [{ artistid: 456, artistname: 'Bob' },{
149149
- The number of rows read so far as part of this SQL `query`. This may increase as you iterate the cursor. The final value is used for [SQL billing](/durable-objects/platform/pricing/#sqlite-storage-backend).
150150
- `rowsWritten`: <Type text='number' />
151151
- The number of rows written so far as part of this SQL `query`. This may increase as you iterate the cursor. The final value is used for [SQL billing](/durable-objects/platform/pricing/#sqlite-storage-backend).
152-
- Any numeric value in a column is affected by the JavaScript's 52-bit precision for numbers. If you store a very large number (in `int64`), then retrieve the same value, the returned value may be less precise than your original number.
152+
- Any numeric value in a column is affected by JavaScript's 52-bit precision for numbers. If you store a very large number (in `int64`), then retrieve the same value, the returned value may be less precise than your original number.
153153

154154
:::note[SQL transactions]
155155
Note that `sql.exec()` cannot execute transaction-related statements like `BEGIN TRANSACTION` or `SAVEPOINT`. Instead, use the [`ctx.storage.transaction()`](/durable-objects/api/storage-api/#transaction) or [`ctx.storage.transactionSync()`](/durable-objects/api/storage-api/#transactionsync) APIs to start a transaction, and then execute SQL queries in your callback.

0 commit comments

Comments
 (0)