Re: Index compression vs. table compression

DA Morgan wrote:

>IF / ELSE / END IF;

>But a very bad design: One table named postal codes will suffice.

Right. What I'm saying is you probably want to have the attribute of country as part of the key, since you don't know that every country in the world will have, uh, globally unique postal codes. And more generally, what used to be small lookup tables now have similar key compounding, so they are not small anymore. The only time I _don't_ see this is small, newly designed standalone apps. Which of course, are done with front-end tool-of-the-month these days. Perhaps others see large apps with small lookup tables, but I don't. How much of that is due to my experience-slant, I couldn't say. Judging from what I see on the web, I think many programmers don't think the postal code through, either they only use referential integrity on their local country, or just leave everything free-form. But hey, does every country have postal codes?

jg

--
@home.com is bogus.
Lost a full billable hour in the post office this morning, picking up
the OpenWorld disks.