aiidateam / aiida_core / 5164 / 8
70%
develop: 74%

LAST BUILD BRANCH: fix_3032_doc_working_importexport
DEFAULT BRANCH: develop
Ran
Files 393
Run time 169min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 62.416% (+0.6%) from 61.808%
TEST_AIIDA_BACKEND=sqlalchemy TEST_TYPE="tests"

Pull #2481

travis-ci

web-flow 
Finalizing work of moving `Node` to new backend interface

A new abstract interface has been defined for `BackendNode` in the
module `aiida.orm.implementation.nodes`. This has subsequently been
implemented for the two current database backends Django and SqlAlchemy.
The role of the `BackendNode` class is to provide a single interface,
independent on the database backend implementation, to store and
retrieve data from `Node` instances in the database. The front end
`Node` class will then only ever interact with the backend entity that
it encapsulates and shall never directly interact with the database
model that is encapsulated within the `BackendNode` class.

This commit deprecates quite a few methods from the old node class,
notably all methods of the variant `*_db_*` that retrieved or set data
directly from the database. These are now part of the `BackendNode`
interface, but since all its methods will operate directly on the
database, the `db` infix has been dropped.

All business logic that does not operate directly on database data, such
as the caching of links and attributes of unstored nodes, is implemented
in the front end ORM class `aiida.orm.node.Node`. Also the biggest part
of the business logic is implemented here, to keep the backend layer
thin and lean.
Pull Request #2481: Migrate `Node` to the new backend interface

21591 of 34592 relevant lines covered (62.42%)

0.62 hits per line

Source Files on job 5164.8 (TEST_AIIDA_BACKEND=sqlalchemy TEST_TYPE="tests")