Question Tables without primary keys
- mlocati
- Topic Author
- Visitor
14 years 6 months ago #1
by mlocati
Tables without primary keys was created by mlocati
I've noticed that two tables, {$TBLPREFIX}dates and {$TBLPREFIX}remotelinks (created in /setup.php at lines 763 and 800) don't have a primary key.
Is this correct?
Is this correct?
Please Log in or Create an account to join the conversation.
- fisharebest
- Offline
- Administrator
Less
More
14 years 5 months ago #2
by fisharebest
Greg Roach - greg@subaqua.co.uk - @fisharebest@phpc.social - fisharebest.webtrees.net
Replied by fisharebest on topic Re: Tables without primary keys
Tables with plural names (e.g. wt_dates) were in the original phpGedView.
Tables with singular names (e.g. wt_name) were added by me (in later versions of phpGedView and in webtrees).
So, you can tell by the name that these ones still need to be reviewed....
I plan to convert the wt_dates table into a wt_fact table. This will include all facts/events, not just those that have a date. It will also contain other event attributes such as places, which will make it possible to search for people born in a particular place, or all people with the same occupation. This table will have a primary key.
wt_remotelinks is just a list of "1 RFN xxx" tags. Once we have the wt_fact table, we will no longer need this.
Later, I plan to combine the common parts of wt_individuals, wt_families, wt_sources, etc. into a single table, wt_record
Tables with singular names (e.g. wt_name) were added by me (in later versions of phpGedView and in webtrees).
So, you can tell by the name that these ones still need to be reviewed....
I plan to convert the wt_dates table into a wt_fact table. This will include all facts/events, not just those that have a date. It will also contain other event attributes such as places, which will make it possible to search for people born in a particular place, or all people with the same occupation. This table will have a primary key.
wt_remotelinks is just a list of "1 RFN xxx" tags. Once we have the wt_fact table, we will no longer need this.
Later, I plan to combine the common parts of wt_individuals, wt_families, wt_sources, etc. into a single table, wt_record
Greg Roach - greg@subaqua.co.uk - @fisharebest@phpc.social - fisharebest.webtrees.net
Please Log in or Create an account to join the conversation.