Changes

Bugfixes

If Prisma was used with an existing Postgres database where ids were numeric, nested mutations were not working in many cases. This bug was addresed by a largescale refactoring. #2647
We implemented an improvement for the connectionLimit setting in the Prisma server config. So far the number of connections was actually the supplied limit times 10, e.g. a setting of 2 was resulting in 20 connections. We implemented a fix so that the setting is obeyed by the Prisma server. We had to introduce a minimum of 2 connections for this setting.
#2640
#2717
6393a29 Rename clusterInfo to serverInfo (#2713)
059157f This PR removes the cluster and local command (#2702)
ab27bca fix: do not allow usage of cluster, service properties together (#2721)
98677d7 fix: offline deploy by moving network error behind debug flag (#2719)
070d7f3 fix: include server name in delete command (#2718)
f58984f fix: validate NDF folder structure (#2722)

Because of a large scale refactoring we were able to enable arbitrary nesting of mutations.
#2647 #1579
The connectors for MySQL and Postgres have been unified into one generic connector. Therefore no subtle differences in behaviour should exist.

BREAKING: The deprecated clusterInfo query has been removed now. It was replaced by the serverInfo query in a previous release. #2714