Skip to content

Commit

Permalink
Update data-type-numeric.md
Browse files Browse the repository at this point in the history
  • Loading branch information
TomShawn committed Jul 15, 2022
1 parent e705bb9 commit fdd2468
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion data-type-numeric.md
Expand Up @@ -121,7 +121,7 @@ The following table summarizes the required storage for floating-point types sup

The `FLOAT` type stores a single-precision floating-point number. Permissible values are -3.402823466E+38 to -1.175494351E-38, 0, and 1.175494351E-38 to 3.402823466E+38. These are the theoretical limits, based on the IEEE standard. The actual range might be slightly smaller depending on your hardware or operating system.

`FLOAT(p)` can be used to represent the required precision in digits. TiDB uses this value only to determine whether to use `FLOAT` or `DOUBLE` for the resulting data type. If p is from 0 to 24, the data type becomes FLOAT with no M or D values. If p is from 25 to 53, the data type becomes `DOUBLE` with no M or D values. The range of the resulting column is the same as for the single-precision `FLOAT` or double-precision `DOUBLE` data type.
`FLOAT(p)` can be used to represent the required precision in bits. TiDB uses this value only to determine whether to use `FLOAT` or `DOUBLE` for the resulting data type. If p is from 0 to 24, the data type becomes FLOAT with no M or D values. If p is from 25 to 53, the data type becomes `DOUBLE` with no M or D values. The range of the resulting column is the same as for the single-precision `FLOAT` or double-precision `DOUBLE` data type.

```sql
FLOAT[(M,D)] [UNSIGNED] [ZEROFILL]
Expand Down

0 comments on commit fdd2468

Please sign in to comment.