What outdated & incorrect info have you found in the Wiki?

Have you found something that seems to be absolutely wrong in the wiki? If you’re not sure enough that it is actually wrong, post a link to it in this thread. Someone in the community should be able to say for certain.

Maybe it is obsolete information. Maybe it is a feature that has to be accessed in a particular way. Maybe the documentation is ambiguous.

Here is my Gramps bafflement for today.

Hopefully it will be the only confusion for the day.

The wiki says that a backup archive can be extracted to a fresh tree via the Manage Family Tree dialog.

I’ve not seen this and don’t know how a user could navigate to the folder with the archive. I suppose you could change the path of the database folder in the Preferences… but then you’d lose access to your other trees.

Is this an old feature that evolved into a different method? The How to restore a backup says its instructions are for v3.3 and later.

The Manage Family Trees sections says that this is only an option with the GNU Revision Control System. (The WHAT?)

If you are using windows then you won’t see the archive button which basically enable a snap shot (archive) feature.

Sorry link dump from googling!

Archiving a Family Tree and Gramps and Windows: Archiving which leads to a closed bug that shows another bug related to windows ( 3125 Any RCS activity causes an exception ) which lead to a discussion on reddit ( Looking for workflow/toolset for storing GrampsXML in online git ) which leads to a feature request to replace RCS with something more modern that windows can use ( 4901 : Add a new storage format base on GIT) !

Also Database_Formats#Versions and old message archiving-problem which may answer your question as someone called Doug mentions about RCS archives:

It organises the backups in a logical tree structure so it’s immediately
obvious which backup comes from which version of the DB and when, and
which you’re loading if you need to use an earlier backup. It saves
having to think how you might name your backups to show their
inter-relationships and then remembering what was the system you used
the year before last or whenever, when the time comes and you need it.

1 Like

That’s the 4th thing I’ve heard the Windoze version of Gramps can’t manage yet is doable in the other OSes.

The others were:

  • remote host and port support for the locating the database remotely
  • network paths without mapping a drive letter assignment
  • environment variables

any more?

this is wrong, it’s no problem connecting to a database on a remote computer as long as you actually use a database engine that support host name and ports.
sqlite do not, it is an in prosess database engine.

I have multiple databases both running on postgresql and mongodb servers that connect with host name or IP address and port number

it is also possible to do so from wsl, wsl2 and from any virtual client.
It is also possible to connect to a server on wsl, wsl2 or any virtual client…

only problem was that there was a change in how it was done from wsl to wsl2 how to connect to the host os.

Thank you. Such clarifications are welcome.

It also helps people understand the reasoning behind previous inquiries about the future of the MongoDB and PostgreSQL add-ons.

I have not tried this for Gramps 5.x, but if it doesn’t work, it is only because Gramps doesn’t support UNC file path, Linux use i.e Samba for this.

But there is many Windows desktop software in general that don’t support UNC, not unique for Gramps, an actually, storing a sqlite database on a network share for read/write is not recommended because of latency, even though sqlite actually support it, regardless if it is a mapped network share or an UNC share. a sqlite database should be stored on the same system the software is run from, not needed to be same drive, just the same system…

I do not see any huge differences storing the database file on my host computer and accessing it from a virtual client on the same computer, but I do see reduction in performance on larger database files stored on network shares vs. local computer, even when the share is fast nvme ssd over 2GB (1+1) paired network.

The latency differences for the same database stored in posgresql remote or local are minimal.
The same is it if the postgresql database is installed on Linux or Wndows, and similar hardware, no noticeable difference.

mongodb drivers needs updates before its any point to do any more speed tests on it.

It should have been interesting to see how Gramps would have performed as graph database software…