Problem
Right now we need to tell people to use prisma init and then open and edit prisma/.env to add their connection string: https://twitter.com/nikolasburk/status/1265617985986801664

This is cumbersome, especially if you just want people to get to a working Introspection as quickly as possible.
Suggested solution
We could add a param --database (or --connection-string or --url or similar) that takes and validates the connection string, extracts the provider (mysql:// => mysql etc) and persists both in the newly generated schema.prisma and .env automatically.
Alternatives
We keep the manual workflow that tells people to edit the file.
Problem
Right now we need to tell people to use

prisma initand then open and editprisma/.envto add their connection string: https://twitter.com/nikolasburk/status/1265617985986801664This is cumbersome, especially if you just want people to get to a working Introspection as quickly as possible.
Suggested solution
We could add a param
--database(or--connection-stringor--urlor similar) that takes and validates the connection string, extracts the provider (mysql://=>mysqletc) and persists both in the newly generatedschema.prismaand.envautomatically.Alternatives
We keep the manual workflow that tells people to edit the file.