aboutsummaryrefslogtreecommitdiff
path: root/doc/src/sgml/ref/create_domain.sgml
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src/sgml/ref/create_domain.sgml')
-rw-r--r--doc/src/sgml/ref/create_domain.sgml14
1 files changed, 10 insertions, 4 deletions
diff --git a/doc/src/sgml/ref/create_domain.sgml b/doc/src/sgml/ref/create_domain.sgml
index bddfb572875..0f52ff67f77 100644
--- a/doc/src/sgml/ref/create_domain.sgml
+++ b/doc/src/sgml/ref/create_domain.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_domain.sgml,v 1.23 2005/09/22 23:56:46 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_domain.sgml,v 1.24 2005/09/23 02:01:35 momjian Exp $
PostgreSQL documentation
-->
@@ -52,10 +52,16 @@ where <replaceable class="PARAMETER">constraint</replaceable> is:
into a single location for maintenance. For example, an email address
column may be used in several tables, all with the same properties.
Define a domain and use that rather than setting up each table's
- constraints individually. <note>Keep in mind also that declaring a
- function result value as a domain is pretty dangerous, because none of
- the PLs enforce domain constraints on their results.</note>
+ constraints individually.
</para>
+
+ <note>
+ <para>
+ Keep in mind also that declaring a function result value as a domain
+ is pretty dangerous, because none of the PLs enforce domain constraints
+ on their results.
+ </para>
+ </note>
</refsect1>
<refsect1>