Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Z1hQs-0005gI-GA for pgsql-docs@arkaria.postgresql.org; Sun, 07 Jun 2015 20:44:38 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Z1hQr-0004QD-Uh for pgsql-docs@arkaria.postgresql.org; Sun, 07 Jun 2015 20:44:37 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Z1hQq-0004Nr-6x for pgsql-docs@postgresql.org; Sun, 07 Jun 2015 20:44:36 +0000 Received: from mail-wi0-x235.google.com ([2a00:1450:400c:c05::235]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1Z1hQj-0006sB-FK for pgsql-docs@postgresql.org; Sun, 07 Jun 2015 20:44:34 +0000 Received: by wibdq8 with SMTP id dq8so65183558wib.1 for ; Sun, 07 Jun 2015 13:44:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=VnYaSVXPdS3sD/5D0AuJloiZDXwDw3V3AEOXGs8GeA4=; b=jFrN8yXRQfI1aiVFTdP6n5Cocmgy0ezTyLpNfh0+9+cihMN/JWkjLkcha0OZlHvkjN a2knRrvgBlPLJ53Ex6Dg+CCSI3hlB6S37FfXeniHMNIayQITKsNtUlzuJ6ijFG4rGYFF I5VxmxRhCb1SepnbiNiIkcIOKMTePC2Y98TM+Rl6/Sfl5il++N0o3/gP/c+sryJYQDm5 qbffKCYiCEl7KpNrCvwjfBp8HMrYNksyQzNPu+DIUDt7nNmmKf9kC/mI8r8Iu7f/wxOh 0sEAR3Fobvk/r7IECQ8jN1U1ZIygBEDaf1cBSaZLBCWzS3gqLKAIOemq4vnECHJc7mdS jXXA== X-Received: by 10.181.29.100 with SMTP id jv4mr15451192wid.4.1433709868058; Sun, 07 Jun 2015 13:44:28 -0700 (PDT) Received: from [192.168.1.2] (ppp-44-124.32-151.iol.it. [151.32.124.44]) by mx.google.com with ESMTPSA id g15sm5087614wiv.22.2015.06.07.13.44.26 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 07 Jun 2015 13:44:27 -0700 (PDT) Message-ID: <5574AD22.8010508@gmail.com> Date: Sun, 07 Jun 2015 22:44:18 +0200 From: Danilo Fortunato User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: pgsql-docs@postgresql.org Subject: What is the meaning of the N string operator ? Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.5 (--) 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 In the SQL code related to Greenplum Database (which is based on PostgreSQL) generated by a query and reporting tool, a noticed a "N" operator put before a lot of strings. For example: case when column_a <> N'#' then column_a when column_b <> N'#' then column_b else NULL end I executed this SQL code, and I found out that it is valid. In the PostgreSQL documentation I didn't find a description of this operator (though it is not easy to search for). However, I found a description of the E (escape) and B (binary) string operators. Can anybody explain the meaning of the N string operator ? Is there a section in the PostgreSQL documentation that describes it ? Thanks, Danilo Fortunato -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs