aiida.backends.djsite package

Subpackages

• aiida.backends.djsite.db package
  • Subpackages
    • aiida.backends.djsite.db.migrations package
      • Submodules
    • aiida.backends.djsite.db.subtests package
      • Subpackages
        • aiida.backends.djsite.db.subtests.migrations package
          • Submodules
      • Submodules
  • Submodules

Submodules

Simple wrapper around Django’s manage.py CLI script.

Utilities and configuration of the Django database schema.

class aiida.backends.djsite.manager.DjangoBackendManager

Bases: aiida.backends.manager.BackendManager

Class to manage the database schema.

__module__ = 'aiida.backends.djsite.manager'

_load_backend_environment()

Load the backend environment.

_migrate_database_generation()

Reset the database schema generation.

For Django we also have to clear the django_migrations table that contains a history of all applied migrations. After clearing it, we reinsert the name of the new initial schema .

_migrate_database_version()

Migrate the database to the current schema version.

get_schema_generation_database()

Return the database schema version.

Returns

distutils.version.StrictVersion with schema version of the database

get_schema_version_code()

Return the code schema version.

get_schema_version_database()

Return the database schema version.

Returns

distutils.version.StrictVersion with schema version of the database

get_schema_version_reset(schema_generation_code)

Return schema version the database should have to be able to automatically reset to code schema generation.

Parameters

schema_generation_code – the schema generation of the code.

Returns

schema version

get_settings_manager()

Return an instance of the SettingsManager.

Returns

SettingsManager

is_database_schema_ahead()

Determine whether the database schema version is ahead of the code schema version.

Warning

this will not check whether the schema generations are equal

Returns

boolean, True if the database schema version is ahead of the code schema version.

reset_backend_environment()

Reset the backend environment.

set_schema_version_database(version)

Set the database schema version.

Parameters

version – string with schema version to set

class aiida.backends.djsite.manager.DjangoSettingsManager

Bases: aiida.backends.manager.SettingsManager

Class to get, set and delete settings from the DbSettings table.

__module__ = 'aiida.backends.djsite.manager'

delete(key)

Delete the setting with the given key.

Parameters

key – the key identifying the setting

Raises

~aiida.common.exceptions.NotExistent if the settings does not exist

get(key)

Return the setting with the given key.

Parameters

key – the key identifying the setting

Returns

Setting

Raises

~aiida.common.exceptions.NotExistent if the settings does not exist

set(key, value, description=None)

Return the settings with the given key.

Parameters

• key – the key identifying the setting

• value – the value for the setting

• description – optional setting description

table_name = 'db_dbsetting'

validate_table_existence()

Verify that the DbSetting table actually exists.

Raises

~aiida.common.exceptions.NotExistent if the settings table does not exist

class aiida.backends.djsite.queries.DjangoQueryManager(backend)

Bases: aiida.backends.general.abstractqueries.AbstractQueryManager

__abstractmethods__ = frozenset({})

__init__(backend)

Parameters

backend (aiida.orm.implementation.sql.SqlBackend) – The AiiDA backend

__module__ = 'aiida.backends.djsite.queries'

_abc_impl = <_abc_data object>

get_bands_and_parents_structure(args)

Returns bands and closest parent structure

get_creation_statistics(user_pk=None)

Return a dictionary with the statistics of node creation, summarized by day, optimized for the Django backend.

Note

Days when no nodes were created are not present in the returned ctime_by_day dictionary.

Parameters

user_pk – If None (default), return statistics for all users. If user pk is specified, return only the statistics for the given user.

Returns

a dictionary as follows:

{
   "total": TOTAL_NUM_OF_NODES,
   "types": {TYPESTRING1: count, TYPESTRING2: count, ...},
   "ctime_by_day": {'YYYY-MMM-DD': count, ...}

where in ctime_by_day the key is a string in the format ‘YYYY-MM-DD’ and the value is an integer with the number of nodes created that day.

query_group(q_object, args)

Subselect to filter data nodes by their group.

Parameters

• q_object – a query object

• args – a namespace with parsed command line parameters.

query_past_days(q_object, args)

Subselect to filter data nodes by their age.

Parameters

• q_object – a query object

• args – a namespace with parsed command line parameters.

aiida.backends.djsite.queries.get_closest_parents(pks, *args, **kwargs)

Get the closest parents dbnodes of a set of nodes.

Parameters

• pks – one pk or an iterable of pks of nodes

• chunk_size – we chunk the pks into groups of this size, to optimize the speed (default=50)

• print_progress – print the the progression if True (default=False).

• args – additional query parameters

• kwargs – additional query parameters

Returns

a dictionary of the form pk1: pk of closest parent of node with pk1, pk2: pk of closest parent of node with pk2

Note

It works also if pks is a list of nodes rather than their pks

Todo

find a way to always get a parent (when there is one) from each pk. Now, when the same parent has several children in pks, only one of them is kept. This is a BUG, related to the use of a dictionary (children_dict, see below…). For now a work around is to use chunk_size=1.

Django settings for the AiiDA project.

Utility functions specific to the Django backend.

aiida.backends.djsite.utils.delete_nodes_and_connections_django(pks_to_delete)

Delete all nodes corresponding to pks in the input.

Parameters

pks_to_delete – A list, tuple or set of pks that should be deleted.