From 21c563c1b5ae0c34d1d3bfc719b0227d9cc9e43c Mon Sep 17 00:00:00 2001 From: Nikolas Date: Thu, 28 Mar 2024 11:44:51 +0100 Subject: [PATCH] Update content/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdx Co-authored-by: Jan Piotrowski --- .../500-deployment/301-edge/450-deploy-to-cloudflare.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdx b/content/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdx index e7026e143d..29da8e4b45 100644 --- a/content/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdx +++ b/content/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdx @@ -27,7 +27,7 @@ The edge-compatible drivers for Cloudflare Workers and Pages are: - [PlanetScale Serverless](https://planetscale.com/docs/tutorials/planetscale-serverless-driver) uses HTTP to access the database - [`node-postgres`](https://node-postgres.com/) (`pg`) uses Cloudflare's `connect()` (TCP) to access the database - [`@libsql/client`](https://github.com/tursodatabase/libsql-client-ts) is used to access Turso databases via HTTP -- [Cloudflare D1](/orm/prisma-client/deployment/edge/deploy-to-cloudflare#d1) is used to access D1 databases via HTTP +- [Cloudflare D1](/orm/prisma-client/deployment/edge/deploy-to-cloudflare#d1) is used to access D1 databases There's [also work being done](https://github.com/sidorares/node-mysql2/pull/2289) on the `node-mysql2` driver which will enable access to traditional MySQL databases from Cloudflare Workers and Pages in the future as well.