2
edits
Changes
→Why no simultaneous access ?
Unlike in 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.
== Why no simultaneous access ?==
From time to time people want to use GRAMPS for collaborative research, and are then stopped as GRAMPS does not allow simultaneous access. That is, you can simultaneously access the database, but this typically results in corrupt data, destroying your database.
The motivation for this is the following:
#We would need a server/client infrastructure, like eg MySQL. However, this is also why MySQL is non-trivial for most users to maintain. We get into system startup files, gramps daemons running, and a whole mess of other stuff. And when you consider that probably under 5% of the users would be interested in something like this, we have to wonder about our return on investment. Is our time more valuable working on other stuff?
#Who to maintain this code? The core developers don't need this feature. Somebody should join the team to make this happen.
Technically, BSDDB can be made to work with a server environment. However, in GRAMPS we give the <code>env.open()</code> the <code>DB_PRIVATE flag</code>. The docs say:
