Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cvcTn-0003Pk-Va for pgsql-docs@arkaria.postgresql.org; Wed, 05 Apr 2017 04:23:36 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cvcTn-0005Nf-Gt for pgsql-docs@arkaria.postgresql.org; Wed, 05 Apr 2017 04:23:35 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cvcTm-0005Hy-4Y for pgsql-docs@postgresql.org; Wed, 05 Apr 2017 04:23:34 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cvcTe-0001Ip-BA for pgsql-docs@postgresql.org; Wed, 05 Apr 2017 04:23:32 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id A4CF320920; Wed, 5 Apr 2017 00:23:25 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Wed, 05 Apr 2017 00:23:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=+y6Q+RMcQ+pqJnAYuwaWem9WmaeT4L40z5BjAno7jog=; b=r8fggmee Wr3OKXtkZe5doHoDlDWMD9tJERfp0e/Q2yBEG4/zrEujr0/LJ+bSgAseAYLekBDl QUBtiRwqDUZDtrDA0qtyAhY2HGFpDpq2CvJ317T44HM7pdCJ3M7WcQOIievclbZs fz4ogUBOVWW9MOyOSqPGoMo8s52UE/gNxHgI/WwiFVDM8ZXuKEjLpH3PS6bkq2C2 X0S5I9GmCoTmiGmcNbTBx8FO4NnTDN5upDaC31yaHKCcXCbbCnxwXfXLoos/sRvK 3ISqQMrVBQojlr6IOaRQm9xgUNsI/oxwp+NZzzORHCcTgBFWPt/7diuveUG6XiAe z+39SjKjT/a6Qg== X-ME-Sender: X-Sasl-enc: bKNI3EY0IVwhmyM9/aC8XADW4C22UuIPucKW8zOzTOPS 1491366205 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 5FEBD7E1DC; Wed, 5 Apr 2017 00:23:25 -0400 (EDT) Subject: Re: CREATE DOMAIN should also include an example of use with functions To: postgresql@eric.brechemier.name, pgsql-docs@postgresql.org References: <20170202204935.1400.31181@wrigleys.postgresql.org> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Wed, 5 Apr 2017 00:23:25 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170202204935.1400.31181@wrigleys.postgresql.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On 2/2/17 15:49, postgresql@eric.brechemier.name wrote: > Page: https://www.postgresql.org/docs/9.6/static/sql-createdomain.html > Description: > > The documentation of CREATE DOMAIN currently describes how optional > constraints can be useful for the fields of a table. There is no mention of > functions in this page. There is an example using operators, which is pretty much the same thing. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs