Database Formats

From Gramps
Revision as of 11:57, 5 May 2016 by Dsblank (talk | contribs) (Why no simultaneous access?)
Jump to: navigation, search


Gramps default data format has evolved over time. Each major change in format usually results in an increase in the major version number.

Gramps 1.0 and earlier

Gramps 1.0 used XML as its default format. This format is portable and easily read by both computers and people. It has two major issues that caused problems when it was used as the default format.

  • Slow to load and save. The entire file had to be parsed to load the data, and parsing XML is not fast. Similarly, to save any changes, the entire file had to be written. People with larger databases (thousands of persons) found the load and save times to be unusable.
  • Consumes a lot of memory. The XML format required that all data be loaded and stored in memory. Larger databases could consume all memory on the system and as a result bring the system to a virtual halt.

Gramps 2.0

To solve the capacity issues, Gramps 2.0 switched to using the Berkeley database, using the ".grdb" extension to identify the file. All database information was stored in this file. This resolved both the load/save time issues and the memory consumption issues. Using a real database backend allowed us to only load the data into memory when we needed it.

The grdb format was a significant step forward for Gramps. However, it was susceptible to data corruption. Since data commits were not atomic (all related changes saved at once), data could get corrupted if an error occurred while a change was being made.

Gramps 2.2

Gramps 2.2 started using the transaction capability of the Berkeley database. This feature ensures that all related data is committed at once. So, if an error occurs while that data is being saved, the database remains intact. Either the entire set of changes makes it to the database, or none of the changes make it.

The problem with the approach in 2.2 is that a single file (the grdb file) is no longer enough for the Berkeley database to handle the data. An "environment" directory is needed to store the transactions log files. A place was needed to keep these files so that the user would not delete them. An environment directory under the ~/.gramps directory was chosen for this. The log files are mapped to the database using the path name of the original grdb file.

This works very well as long as the file is never moved. If the user renames the file, restores a backup of the file, or copies it to another machine, the file will no longer work, since it would no longer correlate to the log files stored under ~/.gramps.

Gramps 3.0

A new approach was taken with Gramps 3.0. While the Berkeley database is still used, the user will no longer see a file. Instead of the actual database file, user opens a symbolic database name. This name will map to a subdirectory under ~/.gramps directory which contains all the needed database files.

Since all the files will be in the same directory, advanced users can make a backup of the entire directory, preserving the entire data. New users, who may not be familiar with the Linux filesystem, will not have to worry about finding their database, since a new Family Tree Manager will replace the old Open File dialog.

Family Tree Manager

The new Family Tree Manager replaces the File Open dialog. Version 3.0 does not work on files, but on Family Tree Databases. Since there is no file to open, a file open dialog makes no sense. The Open button has been replaced with a Family Trees button. Clicking this button brings up the Family Tree Manager, shown below.


The Family Tree Manager allows the user to create a new database, rename an existing database, delete a database, or load a database. All databases appear in the list, so the user does not need to worry about where the databases are located. If a database is open, an icon will appear next to the name.


If the RCS revision control system is installed on your system, Gramps allows you to archive specified versions of your database. To save a version, open the Family Tree Manager and select the opened database. Simply clicking on the Archive button will save the current version to the revision control system. If a database has one or more saved versions, the databases appear as a tree view, with the available versions displayed under them.


In this example, the Gramps Example database has two versions which have been saved. These versions are saved snapshots of your database contents.

The advantage of storing versions is that you can go back to one of these saved versions. To select a version to restore, select the version and click on the Restore button.

Selecting a version to restore

Gramps will extract the version into a new database. The database name is based on the original database name and the revision name.

Restored version

Versions may be deleted and renamed.

Multiple users

Unlike previous versions, Gramps 3.0 supports limited sharing of databases. Multiple users may edit the same database, just not at the same time. The Family Tree Manager will identify a database that is open for another user, and you will not be able to load the database until the other user has closed the database.


Repairing a Corrupt Database

On the odd chance that database corruption occurs, the Family Tree Manager will show the corrupted file with an Error icon next to it. If this database is selected, a Repair button will appear (as seen below).


Clicking the repair button will rebuild the database from the backup files that are automatically created on exit.

Automatic Backup Files

To protect against file corruption problems in the Berkeley database, Gramps 3.0 will generate a backup file at exit if any data has changed.

Unlike in Gramps 2.2, the backup files are not in XML format. The new backup files are a dump of the database tables. This allows the data to be saved quickly. One backup file exists for each primary table in the database. The backup files are not visible to the user, being held in the database directory.

Gramps 5.0

In Gramps 5.0, the database backend became a plugin. This version still uses the same backend as previous versions; however, an new backend is introduced called "DB-API". This is a SQL-based backend. If testing is successful, Gramps 5.1 will use this backend as the default.

You can read more about this back in DB-API Database Backend.

Detailed Changes

This table lists the database changes for each version.

Gramps Database Changes from previous version
Gramps 5.0 18
  • Database backends become plugins
  • BSDDB is default
  • DB-API (SQL) is tested as viable replacement
Gramps 4.2 18
  • added PlaceNames (with Date and Language) Place
Gramps 4.1 17
  • added Tags to Event, Place, Repository, Source, and Citation
  • added alternate names to Place
  • became SourceAttributes
  • Added optional support for checksum on Media object
  • Added PlaceRef and Place Hierarchies
Gramps 3.4 - 4.0 16
  • converted SourceRef to new Citation object
  • Source and Citation objects gained a private flag
Gramps 3.1 - 3.3 15
  • added Tags to Person, Family, and Note
  • added Surname list
  • removed Marker
Gramps 3.0 14
  • added newyear to Dates
  • Replace plain text with StyledText in Notes
Gramps 2.x 13
  • changed name formats

See also