-
Notifications
You must be signed in to change notification settings - Fork 192
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
Simple way to export an entire database #974
Comments
Not sure what others have to say on this, but in my opinion this should even be the default behavior of |
We're working on this - at this stage, I would rather add a |
@szoupanos I think this is very important, in particular since people working with aiida now start to have to back up their stuff for DMPs. P.S. For a first fix, no need to worry about efficiency if this would complicate things - it's just important to have the flag (i.e. something like an equivalent to adding all nodes to group and exporting the group). P.P.S. To also give some thumbs up: There was some work with aiida I did in 2015, which I never exported, so all I had was a DB of an old postgres version and the .aiida directory. I installed the postgres version + aiida 0.12.1, and the migrations + export worked perfectly, so well done with the backwards compatibility! |
Discussion April 17th, 2019:
|
It would be nice if there were a simple way to export an entire AiiDA database.
This would be very useful for collaboration and backup alike.
The text was updated successfully, but these errors were encountered: