# Increase Validation Rules Functionality **URL:** \ **Category:** Product Suggestions\ **Tags:** widget, widget-validation, number-precision\ **Created:** [January 20, 2025, 10:07pm UTC](https://community.tulip.co/t/increase-validation-rules-functionality/13567 "2025-01-20T22:07:42Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![OlgaStroilova](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/olgastroilova/32/7199_2.png) [@OlgaStroilova](https://community.tulip.co/u/OlgaStroilova)\ **Post date:** [January 29, 2025, 5:20pm UTC](https://community.tulip.co/t/increase-validation-rules-functionality/13567/3 "2025-01-29T17:20:03Z")
Great news - we’re working on a decimal place validation rule: > [@Upcoming Release: Numbers Precision](https://community.tulip.co/t/upcoming-release-numbers-precision/13644): > > Dear Tulip Contributors, Great news - We’re excited to announce a much-requested platform update to how we store and preserve numeric data, which we’ll start rolling out as of r306/early February. Details – We’re updating how numbers are represented in Tulip Tables and Completions to support capturing, storing, and displaying trailing zeros, for example, 1.20 versus 1.2. Number data, previously stored in our Postgres database as type [Float](https://www.postgresql.org/docs/current/datatype-numeric.html#DATATYPE-FLOAT), will be stored, moving forward, as a different type … --- _[View the full topic](https://community.tulip.co/t/increase-validation-rules-functionality/13567)._