Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 1CC796501F3 for ; Mon, 8 Dec 2008 12:58:02 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 74409-01 for ; Mon, 8 Dec 2008 12:57:57 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from megazone.bigpanda.com (unknown [64.147.171.210]) by mail.postgresql.org (Postfix) with ESMTP id 1D0416501E6 for ; Mon, 8 Dec 2008 12:57:56 -0400 (AST) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 731523625E; Mon, 8 Dec 2008 08:57:52 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id 709013625D; Mon, 8 Dec 2008 08:57:52 -0800 (PST) Date: Mon, 8 Dec 2008 08:57:52 -0800 (PST) From: Stephan Szabo To: Benjamin Krajmalnik Cc: "Milen A. Radev" , pgsql-admin@postgresql.org Subject: Re: Change in behavior of string concat operator In-Reply-To: Message-ID: <20081208085523.Y47606@megazone.bigpanda.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.1 tagged_above=0 required=5 tests=RDNS_NONE=0.1 X-Spam-Level: X-Archive-Number: 200812/56 X-Sequence-Number: 30889 On Mon, 8 Dec 2008, Benjamin Krajmalnik wrote: > Thanks. > > Then we have an inconsistency between this and the documentation for the > || operator, where it is showing the abilty to concat numeric types > without explicit casting. > > http://www.postgresql.org/docs/8.3/static/functions-string.html What that page appears to say in the note and table is that you can concatenate a string and a non-string like varchar and integer, not multiple non-strings like numeric and integer. What specifically were you looking at on the page?