Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vge15-0000Kd-Dh for pgsql-sql@arkaria.postgresql.org; Wed, 13 Nov 2013 17:14:11 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Vge14-0002Hq-T4 for pgsql-sql@arkaria.postgresql.org; Wed, 13 Nov 2013 17:14:10 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vge13-0002Hj-P5 for pgsql-sql@postgresql.org; Wed, 13 Nov 2013 17:14:09 +0000 Received: from sam.nabble.com ([216.139.236.26]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vge10-00024U-Qz for pgsql-sql@postgresql.org; Wed, 13 Nov 2013 17:14:08 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1Vge10-00007N-0a for pgsql-sql@postgresql.org; Wed, 13 Nov 2013 09:14:06 -0800 Date: Wed, 13 Nov 2013 09:14:06 -0800 (PST) From: David Johnston To: pgsql-sql@postgresql.org Message-ID: <1384362845994-5778192.post@n5.nabble.com> In-Reply-To: <6365.1384360602@sss.pgh.pa.us> References: <20131112181744.GA7522@teak.britvault.co.uk> <20131113130308.GA17439@teak.britvault.co.uk> <20131113141718.GA29223@teak.britvault.co.uk> <20131113142515.GB29223@teak.britvault.co.uk> <52838DF0.8040708@gmail.com> <20131113155113.GA26600@teak.britvault.co.uk> <6365.1384360602@sss.pgh.pa.us> Subject: Re: Function args: TEXT -vs- VARCHAR? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: 1.8 (+) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-sql Precedence: bulk Sender: pgsql-sql-owner@postgresql.org Tom Lane-2 wrote > skinner@.co > (Craig R. Skinner) writes: >> On 2013-11-13 Wed 06:34 AM |, Adrian Klaver wrote: >>> The full SQL type syntax is allowed for input arguments and return >>> value. However, some details of the type specification (e.g., the >>> precision field for type numeric) are the responsibility of the >>> underlying function implementation and are silently swallowed (i.e., >>> not recognized or enforced) by the CREATE FUNCTION command. > >> That's rather vague..... "... some details ..." > > What's ignored by CREATE FUNCTION (and, indeed, pretty much the entire > type inference mechanism) is typmod. So any parenthesized modifier for > a type name is not considered. Usually those are length/precision > constraints, but user-defined types might do something else with them. > >> An explicit table of datatype & what's "silently swallowed" would be >> valuable to clarify this topic that's said to be often repeatedly asked. > > Can't be asked that often, as that text has been untouched for more > than a dozen years ... s/some/parenthetical/ ? David J. -- View this message in context: http://postgresql.1045698.n5.nabble.com/Function-args-TEXT-vs-VARCHAR-tp5777968p5778192.html Sent from the PostgreSQL - sql mailing list archive at Nabble.com. -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql