-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Schema management #27
Comments
One of EdgeDB's goals is live migrations (from roadmap page), so async interface for |
Maybe. We are working on getting https://github.com/edgedb/rfcs/blob/master/text/1000-migrations.rst implemented as soon as possible. Migrations can be quite complicated so they necessitate an interactive process. So far we don't have a good idea how to expose that process as a high-level Pythonic API. We'll see if that's possible once the RFC is implemented and we get some experience with using it. cc @elprans |
Any updates on this one? Looks like there is a working CLI migration functionality now. I deploy my app using docker and it'd be nice to not depend on large edgedb-cli binary just for migrations. |
On the
Most of the binary weight is debug symbols, which we ship while the thing is still in beta for better crash dumps when things go south. A stripped release |
Circling back on this - we are discussing to add a Python entrypoint to run migrations without the CLI. |
For comment:
migrate
orapply_schema
interface (blocking/ not async)export
interface, (also blocking) perhaps something like:My expectation is that these are not likely to and should not be run in an async context, but maybe I'm just not aware of the use case. I would be happy to work on this piece of the project.
The text was updated successfully, but these errors were encountered: