NoMongo: Migration Failure: Permission Denied for Schema Public in develop-postgres Branch

[prayanshchh]

Describe the bug
When attempting to apply database migrations locally on the develop-postgres branch, the process fails with a permission denied for schema public error. The issue occurs even when the PostgreSQL database is correctly set up with the appropriate credentials.

To Reproduce
Steps to reproduce the behavior:

1.Clone the Talawa repository and switch to the develop-postgres branch.
2.Start the PostgreSQL database using valid credentials
3.Run: npm run apply_drizzle_migrations

Expected behavior
Database migrations should be applied successfully, with all required schema and table changes applied to the database.

Actual behavior
The migration fails with the following error:

No config path provided, using default 'drizzle.config.ts'
Reading config file '/path/to/drizzle.config.ts'
Using 'pg' driver for database querying
[⣷] applying migrations...error: permission denied for schema public
    at /path/to/node_modules/pg/lib/client.js:535:17
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at <anonymous> (/path/to/node_modules/src/pg-core/dialect.ts:102:7)
    at NodePgSession.transaction (/path/to/node_modules/src/node-postgres/session.ts:193:19)
    at PgDialect.migrate (/path/to/node_modules/src/pg-core/dialect.ts:95:3)
    at migrate (/path/to/node_modules/src/node-postgres/migrator.ts:10:2) {
  severity: 'ERROR',
  code: '42501',
  file: 'aclchk.c',
  line: '2812',
  routine: 'aclcheck_error'
}

Screenshots

Additional details
similar issue: drizzle-team/drizzle-orm#3353
Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

• Student Internship Programs talawa#359

[prayanshchh]

assign

[xoldd]

@prayanshchh probably a solution to this issue as well: #2855 (comment)

[palisadoes]

@prayanshchh Please close if the other issue fixes this one

[prayanshchh]

my understanding was that app can be booted up locally as well as by docker but as app will be booted up by devcontainers, we won't need this. Closing