Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aUzs1-0006N9-Tx for pgsql-sql@arkaria.postgresql.org; Sun, 14 Feb 2016 16:50:02 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aUzs1-00013c-Go for pgsql-sql@arkaria.postgresql.org; Sun, 14 Feb 2016 16:50:01 +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) (envelope-from ) id 1aUzrz-00011s-AJ for pgsql-sql@postgresql.org; Sun, 14 Feb 2016 16:49:59 +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) (envelope-from ) id 1aUzrw-0002bp-Mp for pgsql-sql@postgresql.org; Sun, 14 Feb 2016 16:49:57 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 98670207D6 for ; Sun, 14 Feb 2016 11:49:55 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Sun, 14 Feb 2016 11:49:55 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=aklaver.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=20lPMOJ9OOewObKBWQaN7PP26ZY=; b=Ys7u7q Kvm10xmnwTk2TqL0hdv7G9oHUkS8p05YOc1CNyyPSwX8EIDz8VSMN1ZXHXd2fB3L G0m+WLTzKXIKntjQwRtvsgvcy7pAGuJx8Dzpfq0EUgEFEmU+gIiqkaRLrieQwdER AQDZjoiyfKJywk7nvzhmDia6n9rRvKr2IZo08= DKIM-Signature: v=1; a=rsa-sha1; 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-sasl-enc:x-sasl-enc; s=smtpout; bh=20lPMOJ9OOewObK BWQaN7PP26ZY=; b=rCc6GGHvljX/iafW5wnoYQioleJA3lzzgqZK3XGc0Ss2xkx SfNP0DBJJClgg12+ZTU0dpR9IAyhoVjEdiDkSuOrCTVQGZ1R0K/xSjKcVnBl4JP5 iPoogH7BD9G4LDhCl+R9iFgf2Pnplq+XYCotqlTSF9YMcBMHyFQKGkpE09aY= X-Sasl-enc: FgHi8O01FSeUMLLojEj2HMXh4yR/jhmIiZNBu/rSdVzq 1455468595 Received: from [192.168.1.2] (174-21-70-246.tukw.qwest.net [174.21.70.246]) by mail.messagingengine.com (Postfix) with ESMTPA id 0380FC00013; Sun, 14 Feb 2016 11:49:54 -0500 (EST) Subject: Re: [ODBC] PostgreSQL: Inserting NULL values adds empty string. To: "Venkatesan, Sekhar" , "pgsql-odbc@postgresql.org" , "pgsql-sql@postgresql.org" References: From: Adrian Klaver Message-ID: <56C0AFEF.70103@aklaver.com> Date: Sun, 14 Feb 2016 08:48:47 -0800 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) 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 On 02/14/2016 05:13 AM, Venkatesan, Sekhar wrote: > Hi Folks, > > I am using PostgreSQL 9.4 odbc driver to talk to 9.4 postgreSQL server. Through what application? > I see that when inserting NULL values into DB is adding empty string in the database only in windows. > The same insert is adding NULL values into database when linux odbc driver is used to connect to linux database. How are you determining this? > Is there any configuration in odbc driver end or in server to retain the null values or is it a bug? > If it is not and is an expected behavior, how to fix it in the application? > > Thanks, > Sekhar > -- Adrian Klaver adrian.klaver@aklaver.com -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql