Elvis Pranskevichus

You can use `edgedb project init --no-migrations` to skip the migration step.

Having an explicit arch support table in docs is a good idea, we'll do this soon. For reference, here's the current platform support table: Server: Target | Description -- |...

@colinhacks, let's have this in the docs/download page in some form.

> The implementation looks solid, but before we merge this I'd like us to reflect a little bit on whether we want `CREATE` to be conditional, because it creates ambiguity...

Hmm. Is there a chance you're restoring into a non-empty database? The bug seems to be that the CLI fails to recognize that the schema is non-empty.

I couldn't reproduce. Steps (as written) attempt `restore` twice into the same db, no?

@colinhacks, I think we need to be much more explicit that `edgedb instance` / `edgedb project` are tools for _development_, not production. Deploying (and hence upgrading) in production depends on...

EdgeDB instance == Postgres cluster EdgeDB database == Postgres database EdgeDB schema module == Postgres schema Currently, when doing major upgrades you must do a dump and a restore (like...

Just in case, EdgeDB cannot run on the smallest Fly.io Postgres.

It should be doable. Even asyncpg was made compatible with trio (https://github.com/python-trio/triopg), and edgedb-python has significantly less magic.