Module db

Author: Fabio Erculiani <lxnay@sabayonlinux.org>

Contact: lxnay@sabayonlinux.org

Copyright: Fabio Erculiani

License: GPL-2

Entropy Framework repository database module. Entropy repositories (server and client) are implemented as relational databases. Currently, EntropyRepository class is the object that wraps sqlite3 database queries and repository logic: there are no more abstractions between the two because there is only one implementation available at this time. In future, entropy.db will feature more backends such as MySQL embedded, SparQL, remote repositories support via TCP socket, etc. This will require a new layer between the repository interface now offered by EntropyRepository and the underlying data retrieval logic. Every repository interface available inherits from EntropyRepository class and has to reimplement its own Schema subclass and its get_init method (see EntropyRepository documentation for more information).

EntropyRepository is the sqlite3 implementation of the repository interface, as written above.

ServerRepositoryStatus is a singleton containing the status of server-side repositories. It is used to determine if repository has been modified (tainted) or has been revision bumped already. Revision bumps are automatic and happen on the very first data "commit". Every repository features a revision number which is stored into the "packages.db.revision" file. Only server-side (or community) repositories are subject to this automation (revision file update on commit).

To Do: migrate to "_" (underscore) convention