* Omnidirectional Query Syntax

Requests that have been moved to the Wish List, or deemed to need no further action
Post Reply
User avatar
GladToBeGrey
Famous
Posts: 115
Joined: 26 Oct 2004 09:16
Family Historian: V7
Location: Dorset, UK

Omnidirectional Query Syntax

Post by GladToBeGrey » 14 Dec 2007 09:54

At the moment the query syntax appears to be uni-directional in respect of the gedcom tree structure; for example, I can start at an Individual, find all their Source Records, and for each Source Record, list all the Multimedia records.

But FH queries cannot do it the other way round; e.g. for a given MM record, find all the Sources referencing it, and them all the Individuals referencing each Source.

It must be possible; FH has the 'Record Links 'Ctrl-L' function available, but currently this only works interactively (and effectively only one record at a time).

This would help enormously for example with producing 'check lists' for maintenance purposes, as well as generally providing a far more flexible query language. It would be so easy with a proper database and SQL ... [wink]

ID:2656

User avatar
Jane
Site Admin
Posts: 8441
Joined: 01 Nov 2002 15:00
Family Historian: V7
Location: Somerset, England
Contact:

Omnidirectional Query Syntax

Post by Jane » 14 Dec 2007 10:51

You can already obtain a list of sources from a Multimedia record, just to a query based on sources and select based on the linked media.

If you use a two stage query with a list save from the first query you can use the standard Individuals linked to Source Query to obtain the people linked to the source found on the first query.

If you really want SQL just load the data in to phpgedview or TNG and use MySQL
Jane
My Family History : My Photography "Knowledge is knowing that a tomato is a fruit. Wisdom is not putting it in a fruit salad."

User avatar
GladToBeGrey
Famous
Posts: 115
Joined: 26 Oct 2004 09:16
Family Historian: V7
Location: Dorset, UK

Omnidirectional Query Syntax

Post by GladToBeGrey » 14 Dec 2007 11:49

OK, but those are both rather techie, clunky, workarounds in my view. Far better to have a decent query syntax that can do it in one step in the first place .... No?

Post Reply