Multiple PlatformaticDB apps inside Runtime with single DB

[akabolov]

Is it possible to use single DB (currently using postgres) with multiple DB services?

Currently, migrations from the second service are not applied to a database, types are not generating, etc.

[mcollina]

What's your usecase?

[akabolov]

2 Platformatic DB apps inside a Runtime and Composed. Both migration sets are existing in <root>/services/service-1/migrations/*.sql and <root>/services/service-2/migrations/*.sql. Env vars PLT_SERVICE-1_DATABASE_URL and PLT_SERVICE-2_DATABASE_URL point to the same local Postgres database. Now I'm applying migration from <root>/services/service-1 by running plt db migrations apply and getting the correct types, etc. from OPENAPI perspective everything is correct for service-1. Then I'm navigating to <root>/services/service-2 and running plt db migrations apply as result no migrations of this service are applied, and local global.d.ts file is REGENERATED with types from service-1, OPENAPI shows entities from the service-1 as well.

[mcollina]

I don’t understand what’s your goal when doing this. Could you clarify?

[akabolov]

I wouldn't say that that is a goal. Initially, I did it this way to simplify local setup.

[mcollina]

a Platformatic DB application maps a SQL database to REST or GraphQL. Once you have it mapped, it does not seem very useful to map it again. That’s why I’m asking why you want to set it up in this way.

[akabolov]

Got it, thank you for your response, and sorry for any inconvenience caused, I was under the impression that Platformatic generates types from SQL directly.

[akabolov]

I've switched to using separate databases (for each service). And now everything works as expected. My question is: Is it possible to use a single database for multiple services for dev purposes?

[leorossi]

You should use platformatic db types on service-2 and that should create types also for service-2.