Commit b04b0163 authored by Thomas G. Lockhart's avatar Thomas G. Lockhart

Remove disclaimer about exact numeric types. They work now!

parent 8a3c7535
...@@ -364,15 +364,10 @@ The sequence will remain in the database until explicitly dropped using ...@@ -364,15 +364,10 @@ The sequence will remain in the database until explicitly dropped using
</caution> </caution>
</para> </para>
<para> <para>
The <firstterm>exact numerics</firstterm> <type>decimal</type> and The <type>int8</type> type may not be available on all platforms since
<type>numeric</type> it relies on compiler support for this.
have fully implemented syntax but currently </para>
(<productname>Postgres</productname> v6.4)
support only a small range of precision and/or range values.
The <type>int8</type> type may not be available on all platforms since
it relies on compiler support for this.
</para>
</sect1> </sect1>
...@@ -412,14 +407,10 @@ then the money type should use the monetary conventions defined for ...@@ -412,14 +407,10 @@ then the money type should use the monetary conventions defined for
</table> </table>
</para> </para>
<para> <para>
<type>numeric</type> <type>numeric</type>
should eventually replace the money type. It has a will replace the money type, and should be preferred.
fully implemented syntax but currently </para>
(<productname>Postgres</productname> v6.4)
support only a small range of precision and/or range values
and cannot adequately substitute for the money type.
</para>
</sect1> </sect1>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment