Moving foreign keys and query json into sql api.

Author: Oxyjun

public/_redirects

@@ -266,7 +266,7 @@
 /d1/build-with-d1/use-indexes/ /d1/best-practices/use-indexes/ 301
 /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/foreign-keys/ /d1/sql-api/foreign-keys/ 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

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

@@ -194,9 +194,9 @@ VALUES
 
 ## Foreign key constraints
 
-When importing data, you may need to temporarily disable [foreign key constraints](/d1/best-practices/foreign-keys/). To do so, call `PRAGMA defer_foreign_keys = true` before making changes that would violate foreign keys.
+When importing data, you may need to temporarily disable [foreign key constraints](/d1/sql-api/foreign-keys/). To do so, call `PRAGMA defer_foreign_keys = true` before making changes that would violate foreign keys.
 
-Refer to the [foreign key documentation](/d1/best-practices/foreign-keys/) to learn more about how to work with foreign keys and D1.
+Refer to the [foreign key documentation](/d1/sql-api/foreign-keys/) to learn more about how to work with foreign keys and D1.
 
 ## Next Steps
 

src/content/docs/d1/reference/migrations.mdx

@@ -42,6 +42,6 @@ migrations_dir = "<FOLDER_NAME>" # Specify your custom migration directory
 
 ## Foreign key constraints
 
-When applying a migration, you may need to temporarily disable [foreign key constraints](/d1/best-practices/foreign-keys/). To do so, call `PRAGMA defer_foreign_keys = true` before making changes that would violate foreign keys.
+When applying a migration, you may need to temporarily disable [foreign key constraints](/d1/sql-api/foreign-keys/). To do so, call `PRAGMA defer_foreign_keys = true` before making changes that would violate foreign keys.
 
-Refer to the [foreign key documentation](/d1/best-practices/foreign-keys/) to learn more about how to work with foreign keys and D1.
+Refer to the [foreign key documentation](/d1/sql-api/foreign-keys/) to learn more about how to work with foreign keys and D1.

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

@@ -391,7 +391,7 @@ Toggles the foreign key constraint enforcement. When `PRAGMA foreign_keys` is se
 
 ### `PRAGMA defer_foreign_keys = (on|off)`
 
-Allows you to defer the enforcement of [foreign key constraints](/d1/best-practices/foreign-keys/) until the end of the current transaction. This can be useful during [database migrations](/d1/reference/migrations/), as schema changes may temporarily violate constraints depending on the order in which they are applied.
+Allows you to defer the enforcement of [foreign key constraints](/d1/sql-api/foreign-keys/) until the end of the current transaction. This can be useful during [database migrations](/d1/reference/migrations/), as schema changes may temporarily violate constraints depending on the order in which they are applied.
 
 This does not disable foreign key enforcement outside of the current transaction. If you have not resolved outstanding foreign key violations at the end of your transaction, it will fail with a `FOREIGN KEY constraint failed` error.
 
@@ -410,4 +410,4 @@ ALTER TABLE users ...
 PRAGMA defer_foreign_keys = off
 ```
 
-Refer to the [foreign key documentation](/d1/best-practices/foreign-keys/) to learn more about how to work with foreign keys.
+Refer to the [foreign key documentation](/d1/sql-api/foreign-keys/) to learn more about how to work with foreign keys.