-
Notifications
You must be signed in to change notification settings - Fork 245
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
ponyorm migration tool #16
Comments
Hi, On Aug 7, 2013, at 11:51 AM, steinster [email protected] wrote:
|
If you need any help with it I would love to help with the project a bit. |
Thank you, I appreciate it, we'll get in touch. On Aug 7, 2013, at 7:27 PM, steinster [email protected] wrote:
|
Hi, |
+1 |
1 similar comment
+1 |
Even third-party tools are still not exist? |
Any specific parts I can try and help with getting this done? I need migrations pretty badly at this point |
Right now we are working on release with full JSON support, and after that we will switch to working on migrations. Hope the initial version will be released soon after that.. |
+1 |
+1, waiting for your staff |
+1 |
@kozlovsky I saw that you pushed the json update! Any word or any suggestions on how I could contribute with some code in the method you have in mind in order to get migrations done quicker. Having to do manual alter tables and indexing is getting to be cumbersome |
Yeah, this is the main missing feature of Pony right now. It's excellent otherwise, but really needs migrations (preferably automatic). |
really needed! |
+1 |
2 similar comments
+1 |
+1 |
Any progress with this topic? |
+1 |
@amalashkevich @kozlovsky Any status update on this? There are approximately a kajillion people waiting on and +1ing this, it would be nice to see where it's going or if we should migrate (pun intended) to another ORM with this functionality. |
The core migration functionality is done, we need approximately two weeks to release the first version |
Thanks for the update! Good to hear. |
Great news! Thank you for your work! |
Keep us posted! |
Hi! Very important feature! Waiting for release) |
In my case this is the only thing that block me for full pass to pony. |
At this moment we have some internal branch which can handle simple migrations (like, adding/deleting entities, attributes and relationships). I hope we can push it to GitHub really soon. But before that we need to do some final review during this week. |
Hi, @kozlovsky and team. Any news on when we can have this migration functionality? Thanks, |
Hi, I just pushed a new branch orm-migrations with the first version of PonyORM migrations. You can read the description of API here: https://github.com/ponyorm/pony/tree/orm-migrations/pony/migrate The code is very raw at this point and not intended for production usage yet, we still need to work on it. I think really simple use-cases for PostgreSQL and MySQL should work, but SQLite support is limited, and merge functionality is untested. Adding entity or attribute should work, but, say, changing inheritance hierarchy or modifying a type of relationship will raise NotImplementedError. Anyway, I hope the working version of migrations is close. |
Thank you for your update, @kozlovsky ! |
Hi @kozlovsky, One question: what's better to install 0.8 version? When do you think 0.8 will be available on pip? Thank you! |
How's migration going now? |
In moment has some alternative for schema migrations on PonyORM? |
I can confirm that migrations is working, if you want to install it via pip currently do the following
All the documentation on how to do migration can be found here Also if you are using pony with flask blueprints, please note ref another issue
|
what is the status of this orm-migrations? when will it be merged upstream. |
+1 |
The way I currently solve the migration problem is by partly using a SQL migration script generator (Liquibase at the moment). I create two schemas with ponyorm, then run them apply them on two different databases, then run the SQL diff tool to generate SQL code (ALTER, etc.) Any additional migration of data itself is done within the python, around the SQL code |
By the way - is a subset of migration scripts already ready for production code? Even that would be great |
@Elijas sounds intense. lots of steps to introduce an error. |
I think so too, but I kinda really want to keep ponyorm :D To make it less error-prone, I'm currently considering using
Are there any other good alternatives to yoyo? For the schema-migrations, as I'd rather migrate data with pony |
I've searched some info about migrations, and why it's a difficult task - I think this article summarizes it best, though you guys might want to look at it, to acquire some sympathy for the @ steinster |
How's migration going now? It's been more than a year since my last check. |
They are working on migrations intensively now again, and expect to release
it during summer. You can help the migrations feature (or the team in
general) by donating money (one time or monthly)
|
Any updates on this? :) |
Even without a full migration tool, is there a mechanism that can be used to do simple column and foreign key additions to a schema in a fairly DB-independent manner? Like the problem seems to become much simpler if you don’t have to worry about renaming or changing data types or the like. |
xref with #563 |
Yay, anybody else here also stuck with Pony ORM because some previous developer picked it without realizing there is no migration support? This issue is almost 8 years old. Should we still have hope or move on? |
@jbvsmo I'd recommend reaching out in their telegram chats - that's a direct line of communication with the developers, you probably will get your to your answer the fastest this way. Although in my personal opinion, I wouldn't advise to keep your hope too up high. |
Just move one guys |
any update on migrations for pony? We'd love to help out. |
updates? |
Hello,
I'm not sure if this is the place to put this question. If there is a better place please let me know.
Is there a DB migration tool for pony orm? Something like alembic for sqlalchemy..
The text was updated successfully, but these errors were encountered: