Re: baseball league db design
From: John O'Conner <jsoconner_at_earthlink.nospam.net>
Date: Sun, 25 Jan 2004 08:51:09 GMT
Message-ID: <1sLQb.26779$zj7.6117_at_newsread1.news.pas.earthlink.net>
>
>
> It seems like the only right way from the point of DB design, but there
> is a slight problem with input; some people will enter street name as
> '4th of July', some 'Fourth of July Street'. If you're prepared to
> handle this...
>
Date: Sun, 25 Jan 2004 08:51:09 GMT
Message-ID: <1sLQb.26779$zj7.6117_at_newsread1.news.pas.earthlink.net>
Karel Miklav wrote:
> John O'Conner wrote:
>
>> One other thing...many of the participants share the same address. For >> example, parents, siblings in the same league, etc. Does it seem >> reasonable to store addresses separately in an Address table? Then >> each participant would have a foreign key to an Address.
>
>
> It seems like the only right way from the point of DB design, but there
> is a slight problem with input; some people will enter street name as
> '4th of July', some 'Fourth of July Street'. If you're prepared to
> handle this...
>
???. I don't understand your comment. '4th of July Street'? I'm sure you are making a good point, but since I really don't have much db experience, I'm not understanding. Why would creating a separate Address table encourage users to write a date into the address?
-- John O'ConnerReceived on Sun Jan 25 2004 - 09:51:09 CET