• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

3NF Question

ChAoTiCpInOy

Diamond Member
I'm having a little difficulty understanding 3NF regarding non-transitively dependency. I have an address say "123 S Grand Ave 544" that was keyed in and I'm storing it as the mailing address. I send that address to Google and get back "123 South Grand Avenue" and store it as the comparison address.

My question is is storing both addresses in the same table considered breaking normalization? If so, why? If not, why?

Thanks in advance.
 
I think it depends what "comparison address" means to you. If the "comparison address" refers only to the key of the table, that's 3NF. If it's related to the mailing address, and stored in a table where the mailing address is not the primary key, that's not 3NF. I'm thinking this is a case where it's not 3NF.

I also think, somewhat frequently, that 3NF is overrated, and dropping to 2NF makes sense.
 
Back
Top