Changes

Jump to: navigation, search

Gramps 3.0 Wiki Manual - FAQ

1 byte removed, 14:23, 25 February 2009
m
Database - GRAMPS file formats: Marked up as definition list.
==Database - GRAMPS file formats==
*;What is the maximum database size (bytes) GRAMPS can handle?:GRAMPS has no hard limits on the size of a database that it can handle. Starting with 2.0.0 release, GRAMPS no longer loads all data into memory, which allows it to work with a much larger database than before. In reality, however, there are practical limits. The main limiting factors are the available memory on the system and the cache size used for BSDDB database access. With common memory sizes these days, GRAMPS should have no problem using databases with [[GRAMPS Performance|tens of thousands of people]]. *;How many people can GRAMPS database handle? :See above. Again, this is dependent on how much memory you have, see [[GRAMPS Performance]]. *;My database is really big. Is there a way around loading all the data into memory?:Starting with 2.0.0 release, GRAMPS no longer loads all data into memory, which allows it to work with a much larger database than before. The fileformat used is <code>.grdb</code> which means gramps database. *;Can I run GRAMPS from a database on a NFS share?:Yes you can. *;Why is the database format not portable?:The biggest issue with GRAMPS portability lies with 'transactions'. WithGRAMPS 2.2, we added support for atomic transactions to protect data.With atomic transactions, multiple changes are committed as a singleunit. Either all the changes make it, or none of the changes make it.You are never left in a situation with a partial set of changes. A sidebenefit of using transactions is that database access (reads and writes)are faster.  :The problem with transactions (at least using BSDDB) is that it does notallow all the data to be stored in a single file. Logging files areneeded to keep track of things. These logging files are kept in a DBEnvironment directory. We need a separate directory for each file,otherwise the log files can interfere with each other.  :In 2.2, we keep the log files under the ~/.gramps/<path> directory,creating a unique directory for each database. The problem is that yourGRDB file needs the log files, which are in a different directory.Copying the GRDB file is only copying a portion of the database.
==Bugs and requests==

Navigation menu