3 ms·
That's why I said "use an API to standardize". I don't see why this is incompatible with having a single field. Unless you actually need the component parts, it
by manigandham 8y ago
That's why I said "use an API to standardize". I don't see why this is incompatible with having a single field. Unless you actually need the component parts, it's much easier to manage than the schema needed for all the variations.
- nradov 8y agoIt's not really practical to call the API every time you need a normalized address. Normalize once and ask for user confirmation, then store the clean address with a separate field per component.
- manigandham 8y agoSure, that's covered by "Unless you actually need the component parts" Either way, yes you should store the clean standardized data and not the input. I didn't think that was confusing. Also you can get the best of both options with a JSON field.