Re: Help! I can't support normalization

From: Rowan <phantomtoe_at_yahoo.com>
Date: 5 Nov 2002 08:32:49 -0800
Message-ID: <4bbf8d70.0211050832.5f67fa4b_at_posting.google.com>


Carl, I would very much appreciate a copy of your presentation. I look forward to reading it. Thanks!

carl.stottlemyer_at_lmco.com (Carl) wrote in message news:<bc814416.0211011302.4e4d120_at_posting.google.com>...
> I was in a situation somewhat similar to yours a couple months ago and
> actually posted a message indicating my frustration. The developers I
> work with were resistant to assigning identification numbers as
> primary keys (which resulted in some non-normailized databases) and
> did not want to use foreign key constraints. Once a week we have
> meetings and during one of the meetings I did a presentation that
> illustrated my argument. The presentation went well and overall most
> people agreed with my arguments. After the meeting most people were
> at least not resistant to my suggestions and some were planning on
> adopting them.
>
> If you would like for me to email you a copy of my presentation I
> would be happy to do that.
>
> As for your first/last name field situation, it may or may not be
> useful to combine last names and first names. If you always want both
> the last name and first name presented the exact same way then you may
> want to combine them in a single field. However, a good argument to
> separate them is if you don't always want both the first name and last
> name. You may also want the fields separated if you sometimes display
> them differently, example: last name, first name or first name last
> name. Another argument to separate them is if you want to sort the
> names with either first and last.
>
> Although some developers are resistant to changing their ways, I think
> that most are open to new ideas if you can support them well.
Received on Tue Nov 05 2002 - 17:32:49 CET

Original text of this message