Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aV16o-0003N9-06 for pgsql-odbc@arkaria.postgresql.org; Sun, 14 Feb 2016 18:09:23 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aV16n-0002PF-Fq for pgsql-odbc@arkaria.postgresql.org; Sun, 14 Feb 2016 18:09:21 +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 1aV16m-0002Oz-QL; Sun, 14 Feb 2016 18:09:21 +0000 Received: from mailuogwdur.emc.com ([128.221.224.79]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aV16j-0004CG-0B; Sun, 14 Feb 2016 18:09:18 +0000 Received: from maildlpprd53.lss.emc.com (maildlpprd53.lss.emc.com [10.106.48.157]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id u1EI9Ce4007724 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 14 Feb 2016 13:09:13 -0500 X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com u1EI9Ce4007724 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1455473353; bh=yNlNN5QOE9xWGK4DzFAFCEOKVhA=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=GoxrgXKBVs3GkD5r89PqIl+X8co/+pcFV0gdKYhq/HUMASDefa6AIAznL0sSIJQMW bzPmXlDAZCBurQEZmeePLUEjug4172Ou0yZu+NjkAhOLwVbcpIOiho6/fPIPV9tLws ymT5ckS9oo/t3sFT1bNuD6u+UCcwhuhDydwPg5NY= X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com u1EI9Ce4007724 Received: from mailusrhubprd02.lss.emc.com (mailusrhubprd02.lss.emc.com [10.253.24.20]) by maildlpprd53.lss.emc.com (RSA Interceptor); Sun, 14 Feb 2016 13:08:48 -0500 Received: from MXHUB108.corp.emc.com (MXHUB108.corp.emc.com [10.253.58.24]) by mailusrhubprd02.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id u1EI8tTt019843 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 14 Feb 2016 13:08:55 -0500 Received: from MX105CL01.corp.emc.com ([fe80::e020:347b:74e3:4176]) by MXHUB108.corp.emc.com ([10.253.58.24]) with mapi id 14.03.0266.001; Sun, 14 Feb 2016 13:08:55 -0500 From: "Venkatesan, Sekhar" To: Adrian Klaver , "pgsql-odbc@postgresql.org" , "pgsql-sql@postgresql.org" Subject: Re: PostgreSQL: Inserting NULL values adds empty string. Thread-Topic: [ODBC] PostgreSQL: Inserting NULL values adds empty string. Thread-Index: AdFnKHSBhR/6qCaDR/mlfXFjFt8rAwASQbqAAAircSA= Date: Sun, 14 Feb 2016 18:08:54 +0000 Message-ID: References: <56C0AFEF.70103@aklaver.com> In-Reply-To: <56C0AFEF.70103@aklaver.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.42.34.192] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Sentrion-Hostname: mailusrhubprd02.lss.emc.com X-RSA-Classifications: public X-Pg-Spam-Score: -4.3 (----) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-odbc Precedence: bulk Sender: pgsql-odbc-owner@postgresql.org It's a C++ application that talks to PostgreSQL DB. I checked the value in = database directly. -----Original Message----- From: Adrian Klaver [mailto:adrian.klaver@aklaver.com]=20 Sent: Sunday, February 14, 2016 10:19 PM To: Venkatesan, Sekhar; pgsql-odbc@postgresql.org; pgsql-sql@postgresql.org Subject: Re: [ODBC] PostgreSQL: Inserting NULL values adds empty string. 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 drive= r 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 th= e null values or is it a bug? > If it is not and is an expected behavior, how to fix it in the applicatio= n? > > Thanks, > Sekhar > --=20 Adrian Klaver adrian.klaver@aklaver.com --=20 Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-odbc