Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why is the database format (GRDB) not portable?

database format portable
0
Posted

Why is the database format (GRDB) not portable?

0

The biggest issue with GRAMPS portability lies with ‘transactions’. With GRAMPS 2.2, we added support for atomic transactions to protect data. With atomic transactions, multiple changes are committed as a single unit. 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 side benefit of using transactions is that database access (reads and writes) are faster. The problem with transactions (at least using BSDDB) is that it does not allow all the data to be stored in a single file. Logging files are needed to keep track of things. These logging files are kept in a DB Environment 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/ directory, creating a unique directory for each database. The problem is that your GRDB file needs the log files, which are in a different directory. Copying the GRDB file

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123