![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I used this for a family tree program I wrote for the web. create table person(ID int, fatherID int, motherID int, gender char(1), dateOfBirth date, dateOfDeath date, detailsOfThePerson varchar(255)); The queries can get a bit complex - eg retrieving a list of second cousins. Recursive code is needed to show more than trivial parts of the whole tree. |
#3
| |||
| |||
|
|
Any suggestions, thoughts? |
#4
| |||
| |||
|
|
Is there a tool that provides metrics on which combinations are most often associated? |
#5
| |||
| |||
|
|
velmurugan_p (AT) yahoo (DOT) com (Velmurugan Periasamy) wrote in message news:<198e6a10.0308061351.48fcd656 (AT) posting (DOT) google.com>... Any suggestions, thoughts? How about a question? Suppose you've got a database. It's all about fishing and the fish you get with different tackle combinations. There are various types of bait, hooks, weights, lines, reels, rods... etc.. OK. So you normalise your database so as to be able to update and retrieve data in any combination. Is there a tool that provides metrics on which combinations are most often associated? I mean, your bait is more often attached to your hook - more often than it is to your reel or rod. There's a natural heirachy of associations. It seems sensible to me to structure your physical database to suit. Baits for hooks for lines for rods etc.. If you want to know the tackle that's best when you're after marlin then there'll be a limited set of related data - as opposed to when you're interested in salmon or trout for instance. Having a table of baits with gnat flys right alongside squid and another with surfcasting rods alongside boat rods etc. seems to me unsophisticated and contrary to common sense. You're never going to be interested in which gnat fly is best for a 50lb strain line. If you normalise the data the poor old SQL engine is going to have to seperate out all the related data to be stored and collate it all again to retrieve it. Wouldn't it be more sensible and efficient to store it as it is meant to be? I'd suggest you'd really want a single item (or record) for marlin with the intrinsic hierachy of bait, hook, line etc. that applies and another similar but quite different item for trout. Btw - does anyone know if Codd's grand-children are allowed to live with their parents? |
![]() |
| Thread Tools | |
| Display Modes | |
| |