On Tuesday 28 October 2003 11:24 am, Dathan Vance Pattishall wrote:
> Think of a binary tree.
>
> Parent_id auto increment
> Child_id
>
> Details of the famly
>
> The head of the family has a child_id == parent_id
>
> All members of the family have different child_ids but the same
> parent_id
>
> T
ECTED]>
Sent: Wednesday, October 29, 2003 1:39 AM
Subject: RE: Ancestry program
> It has been a while since I have looked, but I believe the National
> Genealogical Society has a data model for family tree software. The
> following links are to the NGS and GEDCOM is the file
Around Tue,Oct 28 2003, at 12:15, Nitin, wrote:
> Hi all,
>
> I'm developing a web based ancestry program. The user wants it to be static, that
> means, it isn't for all to use, but his family. Better to say, it'll contain only
> his family tree.
>
> Now,
-Original Message-
From: Dan Greene [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 28, 2003 12:49 PM
To: Nitin; [EMAIL PROTECTED]
Subject: RE: Ancestry program
well... when I do db design, I tend to start with the objects of my system.
The one that comes to mind in your case is people
your user's state/country). Strictly speaking, marrages are not necessary
to trace heritage, but are good info...
> -->From: Nitin [mailto:[EMAIL PROTECTED]
> -->Sent: Monday, October 27, 2003 10:46 PM
> -->To: [EMAIL PROTECTED]
> -->Subject: Ancestry program
&g
- Sr. Programmer and mySQL DBA for FriendFinder Inc.
- http://friendfinder.com/go/p40688
-->-Original Message-
-->From: Nitin [mailto:[EMAIL PROTECTED]
-->Sent: Monday, October 27, 2003 10:46 PM
-->To: [EMAIL PROTECTED]
-->Subject: Ancestry program
-->
-->Hi all,
--
Try doing a web search for the program geneweb. It's done by someone in
France but there are English versions as well. It's freeware. It's a
web based genealogy program and has a built-in database. No need to
reinvent the wheel.
--
MySQL General Mailing List
For list archives: http://lists.my
Hi all,
I'm developing a web based ancestry program. The user wants it to be static, that
means, it isn't for all to use, but his family. Better to say, it'll contain only his
family tree.
Now, I cant think of the proper db design, which will help any user to find his or her
re
