Hardcoded schema name breaks migrations with restricted permissions - Githubissues

medusajs / medusa

Building blocks for digital commerce

https://medusajs.com

MIT License

24.45k stars 2.4k forks source link

Hardcoded schema name breaks migrations with restricted permissions #7058

Open lechinoix opened 4 months ago

lechinoix commented 4 months ago

Bug report

Describe the bug

I setup my medusa store in my production database in a separate schema and I gave it only permissions on its own schema, but when running migrations I had to remove one hardcoded "public" schema name to make it work

System information

Medusa version (including plugins): 1.3.22 Node.js version: Database: Postgres Operating system: MacOS Browser (if relevant):

Steps to reproduce the behavior

Create a user with GRANT ALL ON SCHEMA medusa TO "medusa-user";
Use this user in DATABASE_URL
Run yarn medusa migrations run
It will fail

lechinoix commented 4 months ago

I think we just need to remove the schema here and here