Skip to content

Commit 0a140ab

Browse files
committed
doc: adjust order of NUMERIC arguments to match syntax
Specifically, mention precision before scale Reported-by: claytonjsalem@gmail.com Discussion: https://postgr.es/m/152967566691.1268.1062965601465200209@wrigleys.postgresql.org Backpatch-through: 9.3
1 parent 1d4b73c commit 0a140ab

File tree

1 file changed

+8
-9
lines changed

1 file changed

+8
-9
lines changed

doc/src/sgml/datatype.sgml

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -494,15 +494,14 @@
494494
</para>
495495

496496
<para>
497-
We use the following terms below: The
498-
<firstterm>scale</firstterm> of a <type>numeric</type> is the
499-
count of decimal digits in the fractional part, to the right of
500-
the decimal point. The <firstterm>precision</firstterm> of a
501-
<type>numeric</type> is the total count of significant digits in
502-
the whole number, that is, the number of digits to both sides of
503-
the decimal point. So the number 23.5141 has a precision of 6
504-
and a scale of 4. Integers can be considered to have a scale of
505-
zero.
497+
We use the following terms below: the
498+
<firstterm>precision</firstterm> of a <type>numeric</type>
499+
is the total count of significant digits in the whole number,
500+
that is, the number of digits to both sides of the decimal point.
501+
The <firstterm>scale</firstterm> of a <type>numeric</type> is the
502+
count of decimal digits in the fractional part, to the right of the
503+
decimal point. So the number 23.5141 has a precision of 6 and a
504+
scale of 4. Integers can be considered to have a scale of zero.
506505
</para>
507506

508507
<para>

0 commit comments

Comments
 (0)