feat!: new data proxy activation logic for Prisma 3.15.x

[millsp]

Updates the way the Data Proxy gets activated in the Prisma Client. This will be effective in Prisma 3.15.0.

BREAKING CHANGE:

Prisma peer deps raised to 3.15 and up.

[jasonkuhrt]

Can you update the peer dep requirements https://github.com/prisma/reflector/blob/main/package.json#L77-L80 too.

[millsp]

It looks like const PrismaClientRuntime = params.useDataProxy ? PrismaClientRuntimeProxy : PrismaClientRuntimeLocal came back after the merge.

[janpio]

yay!

[millsp]

I updated the code @jasonkuhrt, can we merge?

[jasonkuhrt]

I wish we had tests on this library :D not yet, but I'm happy the PR comes from basically the most knowledgeable person on 🌍 about Prisma Client :D :D

[jasonkuhrt]

@janpio @millsp I suspect this is outdated now?

reflector/src/Client/controller.ts

Lines 25 to 33 in 373c979

	/**
	* About programmatically passing the connection string.
	*
	* The only way to pass to Proxy Runtime is via inlineDatasources configuration (A).
	*
	* The only way to pass to Local Runtime is via the constructor (B).
	*
	* @see https://www.prisma.io/docs/reference/api-reference/prisma-client-reference#programmatically-override-a-datasource-url
	*/

Is there a simpler way/unified way we can constructure the client for either case now?

[millsp]

URL overrides aren't supported via the constructor yet, unfortunately.

[janpio]

Issue for this: prisma/prisma#11595