|
In practice, zip code is a perfectly acceptable way to identify state, although I suppose there might be isolated cases where this is untrue. But that's not really the issue. Here's the real question: if zip code WERE truly unique to a state, would you remove the state field from your files? I doubt it. There are other examples. Calendar files leap immediately to mind. If you have a situation where you need a simple one-byte flag for every day in a year, do you create a file with a 365-byte array keyed by year, or do you normalize to a daily file keyed by date? The point is simple: like any other technique, database normalization must be addressed as a business decision, and at times strategic denormalization makes sense. Joe > From: Douglas Handy > > Steve, > > > you cant have two towns in the same zip code? > > Yes you can. And in fact a (very) few even cross state boundaries.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
