5 ms·
Why are you normalizing it? Is there some huge performance advantage in having the state field be an Id into a states table? Perhaps it would make updates easi
by lkjhgvbnm 17y ago
Why are you normalizing it?
Is there some huge performance advantage in having the state field be an Id into a states table? Perhaps it would make updates easier if they ever rename Washington?
Why not normalize the name? There must be lots of Johns in your DB
- pyre 17y agoOthers have stated the reason for normalizing it already: interacting with third party software and/or services. It makes more sense to normalize it at the beginning in order to give the user a chance to approve that it was processed correctly. You could just do the normalization at the point when you need to interact with the 3rd-party services, but then it's hidden in the back-end so you have to be confident in your normalization processing. You could roll out a solution where the confirmation page is just there to allow the user to approve that normalization works on their free-form address, but still store it as a chuck of text in the database. Then when you are confident enough in your normalization process, you could just remove the user confirmation part.