[D1, DO] Adding 52-bit limitation for DO and D1 due to JS number (#21738)

* Adding 52-bit limitation for DO and D1 due to JS
number limitation.

* Iterating over feedback.

* Apply suggestions from code review

Co-authored-by: ranbel <[email protected]>

---------

Co-authored-by: ranbel <[email protected]>

Author: 2 people

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

@@ -149,6 +149,7 @@ npx wrangler d1 export <database_name> --remote --table=<table_name> --output=./
 
 - 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.
 - A running export will block other database requests.
+- 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.
 
 ## Troubleshooting
 

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

@@ -98,4 +98,8 @@ return Response.json(returnValue);
   "count": 1,
   "duration": 1
 }
-```
+```
+
+:::note[Storing large numbers]
+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.
+:::

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

@@ -16,7 +16,7 @@ import {
 
 The Durable Object Storage API allows <GlossaryTooltip term="Durable Object">Durable Objects</GlossaryTooltip> to access transactional and strongly consistent storage. A Durable Object's attached storage is private to its unique instance and cannot be accessed by other objects.
 
-The Durable Object Storage API comes with several methods, including SQL, point-in-time recovery (PITR), key-value (KV), and alarm APIs. Available API methods depend on the storage backend for a Durable Objects class, either [SQLite](/durable-objects/best-practices/access-durable-objects-storage/#create-sqlite-backed-durable-object-class) or [KV](/durable-objects/reference/durable-objects-migrations/#create-durable-object-class-with-key-value-storage). 
+The Durable Object Storage API comes with several methods, including SQL, point-in-time recovery (PITR), key-value (KV), and alarm APIs. Available API methods depend on the storage backend for a Durable Objects class, either [SQLite](/durable-objects/best-practices/access-durable-objects-storage/#create-sqlite-backed-durable-object-class) or [KV](/durable-objects/reference/durable-objects-migrations/#create-durable-object-class-with-key-value-storage).
 
 :::note[Recommended SQLite-backed Durable Objects]
 Cloudflare recommends all new Durable Object classes use the [SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage/#create-sqlite-backed-durable-object-class).
@@ -143,12 +143,13 @@ console.log(cursor.toArray()); // prints [{ artistid: 456, artistname: 'Bob' },{
 
 `SqlStorageCursor` has the following properties:
 
-* `columnNames`: <Type text='string[]' />
-  * The column names of the query in the order they appear in each row array returned by the `raw` iterator.
-*  `rowsRead`: <Type text='number' />
-  * 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).
-*  `rowsWritten`: <Type text='number' />
-  * 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).
+- `columnNames`: <Type text='string[]' />
+  - The column names of the query in the order they appear in each row array returned by the `raw` iterator.
+- `rowsRead`: <Type text='number' />
+  - 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).
+- `rowsWritten`: <Type text='number' />
+  - 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).
+- 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.
 
 :::note[SQL transactions]
 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.