3 ms·
> Except stuff like addresses or names, those I intentionally don't push to be normalized IMO, it depends. While the idea of normalizing names is amusing, I pr
by sgarland 1y ago
> Except stuff like addresses or names, those I intentionally don't push to be normalized
IMO, it depends. While the idea of normalizing names is amusing, I probably wouldn't ever push for that either. For addresses, though, I would absolutely normalize everything beyond the street address. If nothing else, it enables you to quite cheaply (from a storage / memory perspective) add a lot of analytics on users that might be useful, but would be expensive to store with every record - things like city population, postal code median income, etc.
And in cases where you need to have your own company's address displayed per-user (disclosures for financial products, for example), it's absolutely a good idea. A full address, especially a business one that might have a Suite, Floor, etc. can easily be 60-80 chars, which over hundreds of millions of rows, adds up.
- Akronymus 1y ago> I would absolutely normalize everything beyond the street address. If nothing else, I'd personally rather store those datums in additional fields/tables, extracted from the address.