Not able to perform graphql queries after changing database to Supabase PostgresQL database

Posted May 22, 2021 1.2k views
Node.jsGitAPIDevelopmentGraphQLDigitalOcean App Platform

I followed this tutorial,in%20GraphQL%20Resolvers, was able to complete it with no issues. After completing it, I tried changing the database to the Supabase PostgresQL, since then I am having issues. I changed the env variable to the database url from the supabase and then I ran npx prisma migrate to sync the prisma schema. When I try the digital ocean api link I am not able to perform any queries. This is the error message I get -
Please advise!

  "errors": [
      "message": "\nInvalid `` invocation:\n\n\n  error: Error validating datasource `db`: the URL must start with the protocol `postgresql://` or `postgres://`.\n  -->  schema.prisma:6\n   | \n 5 |   provider = \"postgresql\"\n 6 |   url      = env(\"DATABASE_URL\")\n   | \n\nValidation Error Count: 1",
      "locations": [
          "line": 11,
          "column": 3
      "path": [
      "extensions": {
        "code": "INTERNAL_SERVER_ERROR",
        "exception": {
          "clientVersion": "2.23.0",
          "stacktrace": [
            "Error: ",
            "Invalid `` invocation:",
            "  error: Error validating datasource `db`: the URL must start with the protocol `postgresql://` or `postgres://`.",
            "  -->  schema.prisma:6",
            "   | ",
            " 5 |   provider = \"postgresql\"",
            " 6 |   url      = env(\"DATABASE_URL\")",
            "   | ",
            "Validation Error Count: 1",
            "    at cb (/workspace/node_modules/@prisma/client/runtime/index.js:35107:17)",
            "    at runMicrotasks (<anonymous>)",
            "    at processTicksAndRejections (internal/process/task_queues.js:97:5)"
  "data": null

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
1 answer

Hi there,

I think that you can not change the connector to supabase:// as it is not a valid connector according to the list with the supported database connectors for Prisma here:

I think that you need to keep postgresql:// as the connector.