Open tvvignesh opened 4 years ago
Would you mind providing a super rough mockup to illustrate your idea?
@schickling Sure. Added below. Hope this gives an idea. One studio instance but multiple db instances. We can have the ability to import schema files or some way to select the location of schema.prisma files and studio can use it to connect from there. Each db can have its own workspace in studio.
Thanks a lot, that definitely clarifies your feature request.
Good news: This will be possible soon via an Electron version!
@schickling That sounds awesome. Had one thought though, it would be even more productive for developers if you have studio running as a VSCode extension. That way, you don't have to switch at all. You can take some inspiration from SQLTools extension for VSCode for the same.
Please create a new issue for this feature request with some pros/cons you have in mind 🙏
Update: I've created an issue myself: #323
Hi. Currently, to have studio connect to different databases (different
schema.prisma
files in different services) running in a microservices pattern, we are having to run separate studio instances.(Also, there is a bug in doing the same for which I have filed an issue here: https://github.com/prisma/prisma2/issues/1209)
It would be great to have one studio instance running but have the ability to specify which database we want to connect to rather than spinning up multiple instances every time.
Thanks.