Changes

From Gramps

GEPS 032: Database Backend API

7 bytes removed, 11:24, 12 May 2015
no edit summary
Exactly what is required for a class to implement a fully functional database for Gramps is only determined by examination of the existing BSDDB class. This involves the following components:
1. # data and metadata update, add, and delete2. # transactions for batch or atomic changes3. # signal handling
Once a full Gramps Database class is created, there needs to be a way of:
1. # selecting which backend to use for new databases2. # selecting the database to load (Family Tree Manager)
We will use the directory structure, as we do now. In each directory, the type of database needs to be identified. This could be done in two ways:
1. # well-defined database backend types. These could be registered, like any plugin/addon.2. # is there really any reason for Gramps to have to have the code for the db backend? All that is necessary is for the backend to create the Database instance.
It makes sense that we will reuse and share the backends, so we should use option 1, and develop a database backend plugin type.
Retrieved from "https://blog.gramps-project.org/wiki/index.php/Special:MobileDiff/54773"

Navigation menu