|
Pages: [1]
|
 |
|
Author
|
Topic: MySQL database help required (Read 195 times)
|
|
|
|
|
Zeb
RootsChat Senior
 Offline
Posts: 431
|
Thanks downside for your reply, I've had a look at your code on your website and Javascript is pretty much out of the question as I just can't get along with it.
When I was programming in assembler years ago I tried to learn C++ and couldn't get my head around it. Now I'd say assembler is the PHP and Javascript is C++ 
The only method I can think of so far is to have one main table called something like "people" containing all the information on each individual like dob, first names, surnames, married name etc. but the problem for me is separating generations & familes with the same surname and also to represent the relationships of one person to another.
Another way I thought of was to create tables with the name or each surname but again, it's how to separate generations & familes sharing surnames and to link relationships of individuals.
I think I'm going to have to create HTML pages for everyone and link them manually... 
|
|
|
|
|
Logged
|
Derby: WOODCOCK (Donnington)
Devon: HARRIS (Plymouth)
Lancashire: DERRICK
Lincolnshire: CROPPER, WOODCOCK (Boston)
London: BARKER, DUGGIN, HARRIS, HINTON, HULBERT, WHITE
Wales: HARRIS, PRITCHARD (Pembrokeshire)
Warwickshire: DERRICK, WOODCOCK
Desperate for my Woodcocks from Birmingham!
|
|
|
Berlin-Bob
Global Moderator
RootsChat Marquessate
Offline
Posts: 5227
by My Daughter. Chatting to find her Roots !
|
Hi Zeb,
just thinking out loud here:
I recently wrote a PHP program to construct descendant and pedigree charts from a GEDCOM file.
http://www.rootschat.com/forum/index.php/topic,143930.msg1134000.html#msg1134000
The idea was, that I only had one HTML page for descendant charts, and on HTML page for pedigree tables.
I did it by reading the GEDCOM file into several arrays, and then using these arrays.
But if I create a database table for each array, and write the GEDCOM directly into that, then I could just as easily read the database to construct the tables ..... which is what I think you are looking for.
I'll think about it (quietly) a bit more, and let you know what comes out.
Bob
|
|
|
|
|
Logged
|
Searching for Coleman, Moore, Kallnung in London; Margulies, Remenyi in E. Europe; Ancestors of Hessie Stevenson-Coleman-Baxter (Ireland, 1861) and, of course, any other ancestors for my web-site. All Census Data included in this post is Crown Copyright (see: www.nationalarchives.gov.uk) |
|
|
downside
RootsChat Aristocrat
Offline
Posts: 2626
Make my day
|
I can't see any way of having less than 2 tables, Individuals and Groups. When I started out a few years ago I tried some of the methods you are examining but they didn't work in the long basically because a family tree is not limited to X number of people. No sooner have you designed a site for 300 individuals, when someone contacts you and you then start adding more and more. It was only when I looked at the structure of a GEDCOM file I realised all I have to do was emulate their file structure and the whole thing worked far more efficiently and with a lot less code.
Individual datafields:
ID, firstName, middleName, surname, sex, birthDate, placeBornTown, placeBornCounty, deathDate, placeDiedTown, placeDiedCounty, DID, AID
DID = DescendencyID (can be blank)
AID = AscendencyID (can be blank)
Group datafields:
GID, husband, wife, progeny, marrDate, marrPlace
The problem is you need a way of displaying the quatity of marriages. If an individual marries more than once and has children with each of those relationships then you need a way of displaying that information. The only way of doing that is with a 2nd table called Groups or Familes.
Incidentally you should not have a field called Married Name because a woman's maidenname is always displayed, even if she marries 2 or 3 times.
|
|
|
|
|
Logged
|
Sussex: Floate, West
Kent: Tuffee
Cheshire: Gradwell
|
|
|
|
|
|
|
|
|
|
Pages: [1]
|
|
|
|
|
