Can you please share your docker-compose file(redact any sensitive information)?

For first error is related to specifying a schema property in the MySQL or Mongo connector which is not supported by them as there is no concept of schema in those database servers. So this issue will be a duplicate of https://github.com/prisma/prisma/issues/4434

For the second issue, please make sure that the user you are using to connect prisma to your database has sufficient right for the creation of new databases and it can also read the existing one. In the above error, Prisma is trying to connect to the "prisma" database which it uses to store metadata information about the datamodel and the migrations that it has applied. Make sure your user has those permissions.

this is my docker-compose.

Can you give more info about the "prisma" database？I need to convince my backend to allow me to connect to his database via prisma. Whether prisma will affect their existing services. I want to know the specific process of prisma connecting to an existing database. Can you give me some links to resources that contain this information?Thanks.
@pantharshit00

"prisma" database stores metadata information about the migrations performed on the server. It also stores some internal tokens. It is not documented as it is an implementation detail. Basically, we query that database and apply the migration accordingly.

So please give your user access to this database so that prisma can work correctly.

@pantharshit00
what is internal token?

It was a legacy feature that we still need to support for compatibility. You can generate the cluster token using prisma cluster-token that is stored in that table to authenticate yourself with the management API.

"prisma" database stores metadata information about the migrations performed on the server. It also stores some internal tokens. It is not documented as it is an implementation detail. Basically, we query that database and apply the migration accordingly.

So please give your user access to this database so that prisma can work correctly.

Is the 'prisma' database just that?
I have deployed Prisma Server through Dokku like this:
https://www.prisma.io/tutorials/deploy-prisma-to-dokku-ct15
But I have named the postgres service 'prismadb' not 'prisma-server-db' - it didn't allow dashes.
Dokku postgres plugin creates a database named the same as the postgres service. So in this case 'prismadb'.
Prisma during deploy creates a 'prisma' database.
I have checked and nothing is stored in the 'prismadb' database. Everything, including my data, is stored in the 'prisma' database.

dokku postgres:connect prismadb
prismadb-# \l
                                 List of databases
   Name    |  Owner   | Encoding |  Collate   |   Ctype    |   Access privileges
   
-----------+----------+----------+------------+------------+--------------------
---
 postgres  | postgres | UTF8     | en_US.utf8 | en_US.utf8 | 
 prisma    | postgres | UTF8     | en_US.utf8 | en_US.utf8 | 
 prismadb  | postgres | UTF8     | en_US.utf8 | en_US.utf8 | 
 template0 | postgres | UTF8     | en_US.utf8 | en_US.utf8 | =c/postgres        
  +
           |          |          |            |            | postgres=CTc/postgr
es
 template1 | postgres | UTF8     | en_US.utf8 | en_US.utf8 | =c/postgres        
  +
           |          |          |            |            | postgres=CTc/postgr
es
(5 rows)

prismadb-# \c prisma
You are now connected to database "prisma" as user "postgres".
prisma-# \dn
        List of schemas
        Name        |  Owner   
--------------------+----------
 booking-check$prod | postgres
 booking-dev$prod   | postgres
 management         | postgres
 public             | postgres
(4 rows)

prisma-# \dt *.*
                        List of relations
       Schema       |          Name           | Type  |  Owner   
--------------------+-------------------------+-------+----------
 booking-check$prod | Account                 | table | postgres
 booking-check$prod | Booking                 | table | postgres
 booking-check$prod | Group                   | table | postgres
 booking-check$prod | Membership              | table | postgres
 booking-check$prod | Room                    | table | postgres
 booking-check$prod | User                    | table | postgres
 booking-check$prod | _AccountOnMembership    | table | postgres
 booking-check$prod | _AccountToGroup         | table | postgres
 booking-check$prod | _BookingToRoom          | table | postgres
 booking-check$prod | _RelayId                | table | postgres
 booking-check$prod | _UserOnMembership       | table | postgres
 booking-dev$prod   | Account                 | table | postgres
 booking-dev$prod   | Booking                 | table | postgres
 booking-dev$prod   | Group                   | table | postgres
 booking-dev$prod   | Membership              | table | postgres
 booking-dev$prod   | Room                    | table | postgres
 booking-dev$prod   | User                    | table | postgres
 booking-dev$prod   | _AccountOnMembership    | table | postgres
 booking-dev$prod   | _AccountToGroup         | table | postgres
 booking-dev$prod   | _BookingToRoom          | table | postgres
 booking-dev$prod   | _RelayId                | table | postgres
 booking-dev$prod   | _UserOnMembership       | table | postgres
 information_schema | sql_features            | table | postgres
 information_schema | sql_implementation_info | table | postgres
 information_schema | sql_languages           | table | postgres
 information_schema | sql_packages            | table | postgres
 information_schema | sql_parts               | table | postgres
 information_schema | sql_sizing              | table | postgres
 information_schema | sql_sizing_profiles     | table | postgres
 management         | CloudSecret             | table | postgres
 management         | InternalMigration       | table | postgres
 management         | Migration               | table | postgres
 management         | Project                 | table | postgres
 management         | TelemetryInfo           | table | postgres
 pg_catalog         | pg_aggregate            | table | postgres
 pg_catalog         | pg_am                   | table | postgres
 pg_catalog         | pg_amop                 | table | postgres
 pg_catalog         | pg_amproc               | table | postgres
 pg_catalog         | pg_attrdef              | table | postgres
 pg_catalog         | pg_attribute            | table | postgres
 pg_catalog         | pg_auth_members         | table | postgres
 pg_catalog         | pg_authid               | table | postgres
 pg_catalog         | pg_cast                 | table | postgres
 pg_catalog         | pg_class                | table | postgres
 pg_catalog         | pg_collation            | table | postgres
 pg_catalog         | pg_constraint           | table | postgres
 pg_catalog         | pg_conversion           | table | postgres
 pg_catalog         | pg_database             | table | postgres
 pg_catalog         | pg_db_role_setting      | table | postgres
 pg_catalog         | pg_default_acl          | table | postgres
 pg_catalog         | pg_depend               | table | postgres
 pg_catalog         | pg_description          | table | postgres
 pg_catalog         | pg_enum                 | table | postgres
 pg_catalog         | pg_event_trigger        | table | postgres
 pg_catalog         | pg_extension            | table | postgres
 pg_catalog         | pg_foreign_data_wrapper | table | postgres
 pg_catalog         | pg_foreign_server       | table | postgres
 pg_catalog         | pg_foreign_table        | table | postgres
 pg_catalog         | pg_index                | table | postgres
 pg_catalog         | pg_inherits             | table | postgres
 pg_catalog         | pg_init_privs           | table | postgres
 pg_catalog         | pg_language             | table | postgres
 pg_catalog         | pg_largeobject          | table | postgres
 pg_catalog         | pg_largeobject_metadata | table | postgres
 pg_catalog         | pg_namespace            | table | postgres
 pg_catalog         | pg_opclass              | table | postgres
 pg_catalog         | pg_operator             | table | postgres
 pg_catalog         | pg_opfamily             | table | postgres
 pg_catalog         | pg_partitioned_table    | table | postgres
 pg_catalog         | pg_pltemplate           | table | postgres
 pg_catalog         | pg_policy               | table | postgres
 pg_catalog         | pg_proc                 | table | postgres
 pg_catalog         | pg_publication          | table | postgres
 pg_catalog         | pg_publication_rel      | table | postgres
 pg_catalog         | pg_range                | table | postgres
 pg_catalog         | pg_replication_origin   | table | postgres
 pg_catalog         | pg_rewrite              | table | postgres
 pg_catalog         | pg_seclabel             | table | postgres
 pg_catalog         | pg_sequence             | table | postgres
 pg_catalog         | pg_shdepend             | table | postgres
 pg_catalog         | pg_shdescription        | table | postgres
 pg_catalog         | pg_shseclabel           | table | postgres
 pg_catalog         | pg_statistic            | table | postgres
 pg_catalog         | pg_statistic_ext        | table | postgres
 pg_catalog         | pg_subscription         | table | postgres
 pg_catalog         | pg_subscription_rel     | table | postgres
 pg_catalog         | pg_tablespace           | table | postgres
 pg_catalog         | pg_transform            | table | postgres
 pg_catalog         | pg_trigger              | table | postgres
 pg_catalog         | pg_ts_config            | table | postgres
 pg_catalog         | pg_ts_config_map        | table | postgres
 pg_catalog         | pg_ts_dict              | table | postgres
 pg_catalog         | pg_ts_parser            | table | postgres
 pg_catalog         | pg_ts_template          | table | postgres
 pg_catalog         | pg_type                 | table | postgres
 pg_catalog         | pg_user_mapping         | table | postgres
(96 rows)

@chemicalkosek

It is the management schema in postgres.

You have two services and the management schema which stores metadata about them

I have already created schema "managment" in my database and granted all permissions to my user, but I stiil receive:

prisma-server_1 | Exception in thread "main" org.postgresql.util.PSQLException: ERROR: permission denied for database mydatabase.

Should I create "prisma" database and create "management" schema in it?

UPD:
I created this database and schema in it and granted permissions,

CREATE DATABASE prisma;
GRANT CONNECT on DATABASE prisma TO testuser;
CREATE SCHEMA IF NOT EXISTS management AUTHORIZATION testuser;
GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA management TO testuser;

but I still receive:

Exception in thread "main" org.postgresql.util.PSQLException: ERROR: permission denied for database mydatabase
Exception in thread "main" org.postgresql.util.PSQLException: ERROR: permission denied for database prisma

@chemicalkosek

It is the management schema in postgres.

There is no such schema by default in postgres

I have solution:

CREATE DATABASE prisma;

ALTER USER testuser CREATEDB

-- switch to database "prisma" --

GRANT CONNECT ON DATABASE prisma TO testuser;
CREATE SCHEMA IF NOT EXISTS management AUTHORIZATION testuser;
GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA management TO testuser;

Now it works for me. Could you specify somewhere in documentation, that user must have permission to create database?

Yes. cc @nikolasburk

�I only want to query the existing database. Can I adjust the configuration of the Prisma and connect to the Prisma with lower permission? I can't get the root access to the database.
@pantharshit00

User should have permission for the creation of the database so that it can create the database for your service.

You can also predict the database name that you will need permission for by looking at the URL in your prisma.yml file. For example:
http://myserver.com/backend/prod

So if you on MySQL database name will be backend@prod and you can give the user permission on prisma and backend@prod db.

On postgres, we will create a schema called backend$prod. Give your user permission on management schema and backend$prod schema.

"prisma" database stores metadata information about the migrations performed on the server. It also stores some internal tokens. It is not documented as it is an implementation detail. Basically, we query that database and apply the migration accordingly.

So please give your user access to this database so that prisma can work correctly.

@pantharshit00
If I only access the existing database and create datamodel.prisma manually, is there any method to avoid to create "prisma" database ?