Open quinchs opened 2 years ago
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.
running the above steps on a clean empty database causes the error so I don't think so
I couldn't reproduce. Steps (as written) attempt restore
twice into the same db, no?
yes
I think that Elvis is correct here: the second restore is trying to restore onto a non-empty database, which I think we typically try to reject in the CLI.
When dumping a database whos schema uses an extension, the returned binary file cannot be used to restore.
Steps to Reproduce:
create a new empty instance
run
edgedb dump ./dump.bin
run
edgedb restore dump.bin
above steps should work as expectedadd a
using extension ..
to the schema and migrate the databaserun step 2 and 3
with testing this im using the edgeql_http extension
Retuned error
``` edgedb error: SchemaError: error initiating restore protocol: Extension ('cb78b832-d624-11ec-b010-f3789a0548ba') is already present in the schemaSchema: