Moving foreign keys and query json into SQL API.

Author: Oxyjun

public/_redirects

@@ -267,12 +267,12 @@
 /d1/build-with-d1/remote-development/ /d1/best-practices/remote-development/ 301
 /d1/build-with-d1/local-development/ /d1/best-practices/local-development/ 301
 /d1/build-with-d1/foreign-keys/ /d1/best-practices/foreign-keys/ 301
-/d1/build-with-d1/query-json/ /d1/best-practices/query-json/ 301
+/d1/build-with-d1/query-json/ /d1/sql-api/query-json/ 301
 /d1/build-with-d1/use-d1-from-pages/ /d1/best-practices/use-d1-from-pages/ 301
 /d1/learning/using-d1-from-pages/ /pages/functions/bindings/#d1-databases 301
 /d1/learning/debug-d1/ /d1/observability/debug-d1/ 301
 /d1/learning/using-indexes/ /d1/best-practices/use-indexes/ 301
-/d1/learning/querying-json/ /d1/best-practices/query-json/ 301
+/d1/learning/querying-json/ /d1/sql-api/query-json/ 301
 /d1/learning/importing-data/ /d1/best-practices/import-export-data/ 301
 /d1/learning/generated-columns/ /d1/reference/generated-columns/ 301
 /d1/learning/local-development/ /d1/best-practices/local-development/ 301
@@ -293,15 +293,15 @@
 /d1/how-to/ /d1/best-practices/ 301
 /d1/how-to/query-databases/ /d1/best-practices/query-d1/ 301
 /d1/how-to/using-indexes/ /d1/best-practices/use-indexes/ 301
-/d1/how-to/querying-json/ /d1/best-practices/query-json/ 301
+/d1/how-to/querying-json/ /d1/sql-api/query-json/ 301
 /d1/how-to/importing-data/ /d1/best-practices/import-export-data/ 301
 /d1/how-to/generated-columns/ /d1/reference/generated-columns/ 301
 /d1/build-databases/ /d1/best-practices/ 301
 /d1/build-databases/query-databases/ /d1/best-practices/query-d1/ 301
 /d1/build-databases/use-indexes/ /d1/best-practices/use-indexes/ 301
 /d1/build-databases/import-data/ /d1/best-practices/import-export-data/ 301
 /d1/build-databases/client-api/ /d1/worker-api/ 301
-/d1/reference/query-json/ /d1/best-practices/query-json/ 301
+/d1/reference/query-json/ /d1/sql-api/query-json/ 301
 /d1/configuration/local-development/ /d1/best-practices/local-development/ 301
 /d1/configuration/remote-development/ /d1/best-practices/remote-development/ 301
 /d1/reference/database-commands/ /d1/reference/sql-statements/ 301

src/content/changelogs/d1.yaml

@@ -195,7 +195,7 @@ entries:
       New documentation has been published on how to use D1's support for
       [generated columns](/d1/reference/generated-columns/) to define columns that are
       dynamically generated on write (or read). Generated columns allow you to extract
-      data from [JSON objects](/d1/best-practices/query-json/) or use the output of other
+      data from [JSON objects](/d1/sql-api/query-json/) or use the output of other
       SQL functions.
   - publish_date: "2023-06-12"
     title: Deprecating Error.cause
@@ -223,7 +223,7 @@ entries:
   - publish_date: "2023-05-17"
     title: Query JSON
     description:
-      "[New documentation](/d1/best-practices/query-json/) has been published
+      "[New documentation](/d1/sql-api/query-json/) has been published
       that covers D1's extensive JSON function support. JSON functions allow you to
       parse, query and modify JSON directly from your SQL queries, reducing the number
       of round trips to your database, or data queried."

src/content/docs/d1/reference/generated-columns.mdx

@@ -6,7 +6,7 @@ sidebar:
 
 ---
 
-D1 allows you to define generated columns based on the values of one or more other columns, SQL functions, or even [extracted JSON values](/d1/best-practices/query-json/).
+D1 allows you to define generated columns based on the values of one or more other columns, SQL functions, or even [extracted JSON values](/d1/sql-api/query-json/).
 
 This allows you to normalize your data as you write to it or read it from a table, making it easier to query and reducing the need for complex application logic.
 
@@ -48,7 +48,7 @@ As a concrete example, to automatically extract the `location` value from the fo
 }
 ```
 
-To define a generated column with the value of `$.measurement.location`, you can use the [`json_extract`](/d1/best-practices/query-json/#extract-values) function to extract the value from the `raw_data` column each time you write to that row:
+To define a generated column with the value of `$.measurement.location`, you can use the [`json_extract`](/d1/sql-api/query-json/#extract-values) function to extract the value from the `raw_data` column each time you write to that row:
 
 ```sql
 CREATE TABLE sensor_readings (

src/content/docs/d1/best-practices/foreign-keys.mdx renamed to src/content/docs/d1/sql-api/foreign-keys.mdx

@@ -74,5 +74,5 @@ results:  [...]
 ## Related resources
 
 - Learn [how to create indexes](/d1/best-practices/use-indexes/#list-indexes) in D1.
-- Use D1's [JSON functions](/d1/best-practices/query-json/) to query JSON data.
+- Use D1's [JSON functions](/d1/sql-api/query-json/) to query JSON data.
 - Use [`wrangler dev`](/workers/wrangler/commands/#dev) to run your Worker and D1 locally and debug issues before deploying.