I'm not convinced 200 is liberal enough for some of that.
For email, a 64 character local part is RFC compliant, then 1 for the '@', and the domain can be 253 characters.
Probably similar edge cases for addresses.
I'm not convinced 200 is liberal enough for some of that.
For email, a 64 character local part is RFC compliant, then 1 for the '@', and the domain can be 253 characters.
Probably similar edge cases for addresses.
The idea I was trying to get across is that of order of magnitude tiers so that you don't end up with VARCHARs of a hundred random lengths.
I tend to think that there is a point where you trade off some correctness for pragmatism. It is true that you could have a user with a 250 character email address, but in a lot of years I've never really seen a legitimate one, and the likelihood is that if you do see one then it's someone doing something weird as opposed to a legitimate customer.
Email is actually one that you might want to just leave as `TEXT` and make sure you're validating with a package, which is something you might want to do anyway. However, I still think it serves as a useful example because most people have a good feel for about how long an email address is.
---