Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bsJtd-00048R-9T for pgsql-interfaces@arkaria.postgresql.org; Fri, 07 Oct 2016 01:24:21 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bsJtc-0007G2-SW for pgsql-interfaces@arkaria.postgresql.org; Fri, 07 Oct 2016 01:24:20 +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_2) (envelope-from ) id 1bsJtK-0006up-EL for pgsql-interfaces@postgresql.org; Fri, 07 Oct 2016 01:24:02 +0000 Received: from mail-pf0-x22e.google.com ([2607:f8b0:400e:c00::22e]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bsJtG-0002FB-BT for pgsql-interfaces@postgresql.org; Fri, 07 Oct 2016 01:24:00 +0000 Received: by mail-pf0-x22e.google.com with SMTP id e6so16694920pfk.1 for ; Thu, 06 Oct 2016 18:23:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=augview-net.20150623.gappssmtp.com; s=20150623; h=from:to:subject:date:message-id:mime-version:thread-index :content-language; bh=EW8v1lVvPRkRDkgKmP2VKkTb4V3gE2FXXBl8fLEpxQs=; b=AUCdGaCCf0d+3HK7I898RgdXqBGKeNAUeZXkuO5LHa3ovhwjVIh+9+J9h3PSLQQ9+b HYOGYPzegu/LXKOhL59n9vQErK4qwk7wEX7EXip6uQzQ1B51XO1PHpWBAA01qsydSIns X1XyEUQ637eWD0guGT6V2X+zB3YCzwrHsE2+CWNbEu9v1bHyFSTBbxI1YefK3pj14pAs 84ZsiBxKj4eYPM9RKEb0zt57FhtoUIBvFyHsHe6327sxY7kQCfie3n9/klJOQI+m2eEn ZqWV7T8zlAjvGoGA3yRiWLE4qZsHCeatsXkfpsjpdmieo1ACwmyCgBIhVqI/b+U/p96r sepQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :thread-index:content-language; bh=EW8v1lVvPRkRDkgKmP2VKkTb4V3gE2FXXBl8fLEpxQs=; b=hePr3ngrSiXEqVCOet9tLlzOjvNtrRTpPOLK/HMYc4drefQcbgRUX/N+8x4BuvpKuC kkfes+0tPHcYVQhs96dfOk8zdqPtzvQgya5aVJUU/pNLzNPpGWC5qRTS77INJshpKoj/ rP+NwrJLR/hOF+SsQEZifeFkjEGyI6TFYLdGI2kV10JGk3Suffkxy3DW30RggEbn4tnV sgd01JW+YWkw/2eddwL1KkY/zP7vUmTTTve7PSyIF4nlxfjgN0S3Zadk60jY7cHocbj5 oUfs+Trc7PDjhf6szCBdSvcIiT7HBWsZ4RAQBgbQb/V3S8BGDbXQc9kaQqHrmWV5PfSX t5lA== X-Gm-Message-State: AA6/9RmOYrGwqwJN0+1ltD7VDYD6HkZxNrY9gwWnykZcOLLeZY24AZzU3P42Tr2cwzQzQP4p X-Received: by 10.98.56.147 with SMTP id f141mr22358059pfa.83.1475803436018; Thu, 06 Oct 2016 18:23:56 -0700 (PDT) Received: from toshibame (125-236-195-177.adsl.xtra.co.nz. [125.236.195.177]) by smtp.gmail.com with ESMTPSA id c4sm25814824pab.5.2016.10.06.18.23.54 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Oct 2016 18:23:55 -0700 (PDT) From: "Attila Peller" To: Subject: cursor updatability changed Date: Fri, 7 Oct 2016 14:23:47 +1300 Message-ID: <002201d22039$7542c320$5fc84960$@augview.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0023_01D220A6.6C3C5940" X-Mailer: Microsoft Outlook 15.0 Thread-Index: AdIgOWHYkLtdp9LDSuqp7NXEx2FnoQ== Content-Language: en-nz X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-interfaces Precedence: bulk Sender: pgsql-interfaces-owner@postgresql.org This is a multipart message in MIME format. ------=_NextPart_000_0023_01D220A6.6C3C5940 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, We are using the latest postgres odbc driver from our software to communicate with external postgres database. After every insert or update operation we are getting a "cursor updatability changed" warning message. I know that this is a warning only and it can be ignored, but the part of our software I don't have access to, always reports it. Any way to supress this message on the ODBC driver level or on the postgres server? I've searched for the problem, but couldn't find any solution. Thanks for any help! Regards, Attila ------=_NextPart_000_0023_01D220A6.6C3C5940 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

We are using = the latest postgres odbc driver from our software to communicate with = external postgres database.

After = every insert or update operation we are getting a “cursor = updatability changed” warning message.

I know that this is a warning only and it can be = ignored, but the part of our software I don’t have access to, = always reports it.

Any way to supress = this message on the ODBC driver level or on the postgres server? = I’ve searched for the problem, but couldn’t find any = solution…

Thanks for any = help!

Regards,

Attila

------=_NextPart_000_0023_01D220A6.6C3C5940--