menu

EdgeDB

Bringing state-of-the-art database technology to the masses.

Channels
Team

Migrating from Alpha 2 -> 3

June 14, 2020 at 2:24am
The EdgeDB community has a new home. This thread is preserved for historical purposes. The content of this conversation may be innaccurrate or out of date. Go to new community home →

Migrating from Alpha 2 -> 3

June 14, 2020 at 2:24am
Alpha 3 offers some really clean features and a high-quality user experience with its updated CLI interface. Is there a clean path to migrating database dumps (or something similar) from an Alpha1 or Alpha2 instance to Alpha3?

June 14, 2020 at 2:33am
You should be able to do edgedb dump in alpha 2 and restore it in alpha 3.
  • reply
  • like
Thank you for verifying this, but now this raises some additional questions. Earlier today, I ran the dump -> restore process whereby I mounted the database dump-file ("dumpMigration.edb") onto a Docker's shared data volume directory, but got an interesting error resembling EdgeQLSyntaxError which complained about a bad semi-colon, but it didn't specify where the ' ; ' vagabond was hiding (i.e. column or line). Any suggestions?
  • reply
  • like

June 14, 2020 at 5:02pm
EdgeQLSyntaxError which complained about a bad semi-colon
Interesting. Would it be possible for you to share the dump file with us?
  • reply
  • like

June 22, 2020 at 10:32pm
EdgeQLSyntaxError which complained about a bad semi-colon
Interesting. Would it be possible for you to share the dump file with us?
Certainly, I've just sent it to 'hello'.
  • reply
  • like
Hm, I was able to restore the DB just fine with edgedb -d tmp restore ~/Downloads/migration.edb
  • reply
  • like
I made a mistake; sending over the actual one -- titled "edb-migration.edb". It has about 50+ kilobytes in size.
Edited
  • reply
  • like
There's indeed an error, although not a syntax one. The problem is that a2 had a bug that caused it to produce dump DDLs with misordered CREATE/ALTER DUMP.
will take a look if he can backport the fix to a2 and issue a bug fix release so that you could make a new dump.
I also have an idea on how to help us better detect this kind of bugs: https://github.com/edgedb/edgedb/issues/1489
  • reply
  • like
Duly noted; thanks Yury. Please let me know if there's anything else you need in the meantime.
  • reply
  • like
We also found the cause of the syntax error you saw -- that was fixed in a3
like-fill
1
  • reply
  • like