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.

Sign up for GitHub

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

Jump to bottom

Consider replacing Django with SqlAlchemy as ORM #123

Closed

aiida-bot opened this issue Dec 10, 2014 · 1 comment

Labels

priority/critical-blocking

aiida-bot commented Dec 10, 2014

Originally reported by: Boris Kozinsky (Bitbucket: bkoz37, GitHub: Unknown)

4 Major Advantages:

Very general query structure for joins and filters across multiple graph links
Single-table inheritance support on query level - can directly cast data objects to correct type
Support for jsonb in Posgres 9.4 provides ability to query within JSON attached as attribute to any node in DB. Very powerful for property lookups
Unit of work architecture gives transaction support (sessions) that is also thread-safe

This would require supporting only Postgres, which is the best DB choice anyway.

Bitbucket: https://bitbucket.org/aiida_team/aiida_core/issue/123

aiida-bot added priority/critical-blocking proposal labels

giovannipizzi removed the Third (major) release label

Member

giovannipizzi commented Jan 19, 2017

SQLAlchemy is now implemented as a second backend, and will be released as stable soon, so I close this.

giovannipizzi closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment