How can I choose database backend?

Development
1

When you press New in Family Trees>Manage Family Trees, a new line is added to the list, the new entry is highlighted (selected) and the cursor is positioned in teh name column. A new name can be entered but as soon as you leave this column, the new tree is recorded and you can’t change any other property, notably the Database Type.

Code suggests this “type” can be chosen from a drop down menu.

It would be nice if I could set this “type” when I create the family tree because I am designing another DB backend. Being able to specify the “type” on creation would allow for easier comparison of backends and make sure compatibility is preserved.

I know I can preset the DB type in Edit>Preferences, Family tab but this requires many clicks.

I assume that the present behaviour is a consequence of BSDDB deprecation but it is very inconvenient to explore new tracks.

Is there a way to remain in “entry mode” to be able to change the DB type and then press some button to notify Gramps we’re done with the definition of a new tree?

2

Given the rarity of changing database backends, the coding burden to eliminate a few extra clicks probably has not been considered worth the tradeoff.

It is actually surprising that there is a contextually driven Convert button in the Family Trees dialog for changing datase backend of a tree rather than a plugin Tool for that purpose.

720×367 30.8 KB

https://www.gramps-project.org/wiki/index.php/Gramps_5.1_Wiki_Manual_-_Manage_Family_Trees#Converting_a_BSDDB_Family_Tree_to_SQLite

Perhaps you could hack the code so that the
Convert button is always available when running in optimise python option Developer mode? And then add pop-up menu for Database backend selection in the convert confirmation dialog?

3

A new tree is created before it is displayed in the list. When you edit the name, only the contents of the name.txt file are changed.

We want to encourage the use of the default database backend which is why a choice is not given in the family tree manager.

In your case, I suggest that you modify the code to add an extra “New” button.

4

Thanks to both of you.

@emyoulation I have disabled the Convert button for the DBs under my new backend as a “safety” precaution. This is why I didn’t think about it.

@Nick-Hall I felt this was the reason. But I intend to have several backends once I’m satisfied with my present implementation: SQLite (pure SQL), MariaDB, PostGRES, … so that the choice is not limited.

Meanwhile, I exported to XML and reimported, only to discover that some backreferences were missing (the import filter does a very good job in checking for consistency). I still have a lot to do.

5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.