# Why do some fields have a varchar precision of 191 for modUserProfile in the modx schema?

**URL:** <https://community.modx.com/t/why-do-some-fields-have-a-varchar-precision-of-191-for-moduserprofile-in-the-modx-schema/940>\
**Category:** Development\
**Created:** [June 5, 2019, 4:40pm UTC](https://community.modx.com/t/why-do-some-fields-have-a-varchar-precision-of-191-for-moduserprofile-in-the-modx-schema/940 "2019-06-05T16:40:35Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jeffmiranda](https://community.modx.com/user_avatar/community.modx.com/jeffmiranda/32/392_2.png) [@jeffmiranda](https://community.modx.com/u/jeffmiranda)\
**Post date:** [June 7, 2019, 3:27am UTC](https://community.modx.com/t/why-do-some-fields-have-a-varchar-precision-of-191-for-moduserprofile-in-the-modx-schema/940/4 "2019-06-07T03:27:03Z")

</div>

Thanks @markh and @digitalpenguin, that makes sense!

Why then doesn’t it apply to the other fields? For instance, _city_ has a precision of 191, but _state_ has a precision of 25. Why the discrepancy?

(Also, I’m asking with the utmost respect for the MODX team. I’m relatively new to DB design and I’m trying to understand the rationale behind certain decisions to further my own knowledge.)

---

_[View the full topic](https://community.modx.com/t/why-do-some-fields-have-a-varchar-precision-of-191-for-moduserprofile-in-the-modx-schema/940)._