Re: Crash when using 'Use Declare/Fetch' and the result set does contain one row only

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Jan-Peter Seifert <Jan-Peter(dot)Seifert(at)gmx(dot)de>, pgsql-odbc(at)postgresql(dot)org
Subject: Re: Crash when using 'Use Declare/Fetch' and the result set does contain one row only
Date: 2014-06-23 12:15:52
Message-ID: 53A81A78.6030409@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

On 06/23/2014 07:58 PM, Jan-Peter Seifert wrote:
> Hello,
>
> Recently we switched from using plain SQL for transaction handling to the corresponding ODBC functions. Now the application crashes if 'Use Declare/Fetch' is checked in the ODBC DSN. Not everytime but when the result set does contain one row only. The course of action leading to the crash is:
>

Any chance of a self-contained, compileable example that demonstrates this?

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Michael Paquier 2014-06-23 12:22:24 Re: Crash when using 'Use Declare/Fetch' and the result set does contain one row only
Previous Message Jan-Peter Seifert 2014-06-23 11:58:51 Crash when using 'Use Declare/Fetch' and the result set does contain one row only