I'm trying to use Data Proxy with lambda and getting the error

Invoke Error 	{"errorType":"Error","errorMessage":"error: Error validating datasource `db`: the URL must start with the protocol `postgresql://` or `postgres://`.\n  -->  schema.prisma:9\n   | \n 8 |   provider = \"postgresql\"\n 9 |   url      = env(\"DATABASE_URL\")\n   | \n\nValidation Error Count: 1","clientVersion":"3.6.0","stack":["Error: error: Error validating datasource `db`: the URL must start with the protocol `postgresql://` or `postgres://`.","  -->  schema.prisma:9","   | "," 8 |   provider = \"postgresql\""," 9 |   url      = env(\"DATABASE_URL\")","   | ","","Validation Error Count: 1","    at Object.request (/node_modules/@prisma/client/runtime/index.js:39051:15)","    at Runtime.IY (/lib/lambdas/cognito/preSignUp.ts:25:23)"]}

• Generated 3.9.0 client with

PRISMA_CLIENT_ENGINE_TYPE='dataproxy' prisma generate

• Set my

DATABASE_URL

to

prisma://....

• Set

previewFeatures = ["dataProxy"]

in

generator client {}

What am I missing here?

Hello everyone, I'm self taught and not an experts at db so I'd really appreciate your help with this:

I've pretty much lost all ability to see my production data visually because cloud.prisma.io keeps failing

Invalid string length
RangeError: Invalid string length
    at JSON.stringify (<anonymous>)
    at _t.serialize (<https://cloud.prisma.io/studio/assets/index.js:1:49045>)
    at _t.update (<https://cloud.prisma.io/studio/assets/index.js:1:12197>)
    at Cc (<https://cloud.prisma.io/studio/assets/vendor.js:50:6994>)
    at _t.n (<https://cloud.prisma.io/studio/assets/vendor.js:50:6688>)
    at _t.update (<https://cloud.prisma.io/studio/assets/index.js:1:48902>)
    at Cc (<https://cloud.prisma.io/studio/assets/vendor.js:50:6994>)
    at _t.n (<https://cloud.prisma.io/studio/assets/vendor.js:50:6688>)
    at <https://cloud.prisma.io/studio/assets/index.js:1:82105>
    at Array.forEach (<anonymous>)

Reopening the studio or even the tab has no effect

Are there any other similar data browsers that you know of which I can use where you can see the relations between the data visually?

Recently, I linked PDP to a project that the company is developing. It is good to have a good DB query statement execution space right away, but I hope there is something better to utilize the query statement of the prisma. The tools we used recently were many programs that linked charts using SQL query statements. • evidence.dev - SQL query statement + MDX is a service that allows monthly statistical reports to be drawn in the form of records. Once you have created a template, you can generate the report immediately on any date. • budibase.com - Administration dashboard created with SQL query statements only. I think it would be great if PDP allows Prisma's query statement results to be directly linked to the chart. It would be great if you could use Prisma's simple query statements to analyze or organize some data. There are many very high quality charts among open sources. • airbnb.io/visx/gallery • <https:nivo.rocks|nivo.rocks> • apexcharts.com I believe the usage will increase exponentially even if we can simply link the chart to the query statement result of the prismatic data platform. And I think it will be the best if it becomes MDX form like evidence.dev.

Hi everyone, I have a theory question. If a web app were to use Prisma Data Proxy with a Postgresql DB, wouldn't it suffer from bad performance due to network latency? (Thinking about the latency of the request to the Data Proxy and the proxy to the DB, and then all of that back). To use a more concrete example, suppose I had an app in Workers (Cloudflare) talking to the Proxy (AWS) talking to some Postgresql DB (GCP), could a scenario like that make CRUD operations in the web app really slow? And if so what's a recommended way to not incur high latencies through this technology? Many thanks in advance.

Hello, I am running to an issue in my

schema.prisma

file. So I configured my app to using data proxy provided, and used the the provided

prisma://....

as DATABASE_URL connection string in my

schema.prisma

file. However, When I tried migrating the models

npx prisma migrate dev

- I got this error:

Error: Get config: Schema Parsing P1012
error: Error validating datasource `db`: the URL must start with the protocol `postgresql://` or `postgres://`.
--> schema.prisma:8
|
7 | provider = "postgresql"
8 | url = env("DATABASE_URL")
|
Validation Error Count: 1

How do I fix this?

There is a bug in the client-side code in Prisma Cloud that doesn't allow users to access the setting page of the project. The screenshots are attached in the next message

Hi @Austin, is it possible to do

prisma db push

with only the

prisma://...

URL as the

datasource.db

, and using

PRISMA_CLIENT_ENGINE_TYPE=dataproxy

? Asking, because I'm getting the following error:

$ prisma db push
Error: Get config: Schema Parsing P1012

error: Error validating datasource `db`: the URL must start with the protocol `mysql://`.

I'm assuming the correct use case is, that I'd need to use the

mysql://

URL locally (because TCP works in local dev environments anyway), and then I may use the

prisma://

URL in prod (e.g. in a serverless environment, because generally only HTTP connections are allowed there) Full config:

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["referentialIntegrity", "dataProxy"]
}

datasource db {
  provider             = "mysql"
  url                  = env("DATABASE_URL")
  referentialIntegrity = "prisma"
}

This message was deleted.

I think something might have changed since this tutorial was written: https://www.prisma.io/docs/guides/deployment/deployment-guides/deploying-to-cloudflare-workers. Using

event.waitUntil

doesn't end up creating logs, but if I just straight

await

the call, it works. Obviously a Cloudflare change, but just FYI

Hello, please I'm trying to set up a planetscale database, but its throwing a 500 error, here https://cloud.prisma.io/projects/create, but its throws a 500 error, with message

We were unable to finish your PlanetScale project setup: Failed to reset database. Response code 500

. Is there a way around this?

Interested in our platform’s pricing? 👇 I’d love share our upcoming pricing and billing model ahead of the platform’s GA launch and get your input. I’d also like to learn more about your use case. The call will only last for max. 30 minutes and it’s a unique opportunity for you to learn more about our plans and provide feedback. If you are up for it, here is the scheduling link: https://calendly.com/alberto-prisma/30-min-zoom-pdp

<!channel> ☝️

Hey! FYI, if you try creating a new project with a mongo connection string that doesn't have a database, the project creator goes ahead and creates some pieces of the project, then hangs and quits in the background with a 500. You're then left with an orphan project and no easy way to delete it (other than directly going to /settings in the browser). Maybe a tiny validator would help with this? I spent too long trying to figure out what was going on before I noticed

Atlas' default connection string doesn't have DBs, hence the confusion.

Are there plans to support MongoDB database provisioning in the future on Atlas?

Hi guys, is it possible to use Prisma Data Platform with Bitbucket? Why it’s restricted to the GitHub? We don’t use GitHub for code management. Are there any plans to add support for Bitbucket?

Hi there, @Vladi Stevanovic mentioned over email that this channel might be a good place for help. 🙂 My account seems to be in a bad state -- whenever I try to Oauth using GitHub, I get a 500 error. Every time, no matter what computer, browser, etc. I use. Here's a video: https://drive.google.com/file/d/1tbT0AjjefmLY5h1t5Nt4B_xcJlsoR5iQ/view

Does the Prisma Data Proxy now work with interactive transactions?

Any ETA on more regions support? Really looking forward to having a SA region!

getting a lot of these

prisma:error Error while querying: HealthcheckTimeout
Error while querying: HealthcheckTimeout
prisma:warn This request can be retried
This request can be retried
prisma:warn Retrying after 240ms
Retrying after 240ms

any idea what a HealthcheckTimeout is?

Hi! I recently discovered this platform thanks to one of your devs. I think this is a great tool for taking Prisma to the next level. I love Prisma, but there is one tricky thing with it and that is migrations. In theory they are simple but things can go wrong as we all know. For example, in my project the version controlled migrations have diverged from the production database's migrations. Schema is still the same, but it is a scary feeling. I think the Data Platform would benefit greatly from having some migrations tools, some ideas off the top of my head: • Doing schema migrations (migration is applied to production DB, and then migration file is pushed to repository) • See diff between version controlled migration files and actual applied migrations in production DB • Rollback migrations • Tool for "syncing" version controlled migration and production DB migrations

Hello! I have successfully configured a development and production environment using Prisma Data Platform, PlanetScale for the DB, and Vercel for deployment. I wanted to recreate this setup for an article and video tutorial so others can do the same, but my production data and development data are linked via PlanetScale's connection string for each respective branch (i.e development branch in PlanetScale links to the development environment in Prisma Data Platform and same for production). While attempting to recreate my initial successful set-up, the development and production environments share the same data (i,e I create a new user in development, and that new user is also created in production). This is obviously not the intended behaviour and while the setup is nearly identical, the main difference I've seen in my tutorial project is the listed development environment has a Data Proxy with AWS and a Database with MySQL and the same is for production. Now, with my successfully set up project, the development environment has a Data Proxy with AWS and a Database with MySQL and the production environment has a Data Proxy with AWS and a Database with PlanetScale MySQL. Now the reason for this is during the creation of the tutorial project, it tried to automatically provision a PlanetScale DB, but I couldn't as it thought I was using my other PlanetScale account (I wasn't even signed into that one so maybe there's a cache issue?) and I hit my limit of 1 database. So I just chose the Use my own database option and provide the PlanetScale connection string. So despite providing a connection string for each respective PlanetScale branch, my current theory is that the connection string is the same for each environment, which is why each environment is bleeding data to each other. I'll provide photos for more context, but if there are any Prisma Developer advocates who want to look further into this, feel free to DM and I'll be more than happy to discuss or even show it via a Zoom call.

When will there be more regions support for the Data Proxy (sa-east in particular)? I'm getting unbearable cold start times with a ~500 lines schema file and I'm wondering how I'm going to deploy to production with this kind of performance.

Big fan of the query console on prisma cloud! Is there anyway for me to use an interactive prisma query console for my local dev db? Even being able to fire of queries from a node console would be good enough

Is it possible to use @updatedAt for Optimisc Concurrent Control? Like

update({ where: { updatedAt: ... } })

.

Hi, I’m looking into using the Prisma Data Proxy for the connection pooling benefits.. However my DB is in a private subnet and I’d like to keep it private. Is there a way to hook up the DataProxy to a private DB? Also is there a way to deploy the data proxy via AWS CDK? All of my infra is on the CDK and it seems pretty weird to have this custom configured thing….

👋 Hello everyone! To streamline support for the Prisma Data Platform, we're archiving this channel and keeping only our 📩 main form of support: opening a ticket 💌 through the Prisma Data Platform UI (cloud.prisma.io). If, for some reasons, you're unable to login, but still need help, you can contact us at support@prisma.io! 👉 Don't hesitate to contact us if you have any questions, feedback or ideas!