| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | Jan-Peter Seifert <Jan-Peter(dot)Seifert(at)gmx(dot)de>, PostgreSQL mailing lists <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:22:24 |
| Message-ID: | CAB7nPqQA-9fTfYXQVEZq2f-FFOBginv6JmNNz12St+j5imu5vA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
On Mon, Jun 23, 2014 at 9:15 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> 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?
>
If possible, something integrated within the regression test infrastructure
in test/ would be nice. A backtrace would be a good addition as well.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Natasha Gajic | 2014-06-23 19:33:05 | Inquiry regarding modification of Postgresql ODBC driver |
| Previous Message | Craig Ringer | 2014-06-23 12:15:52 | Re: Crash when using 'Use Declare/Fetch' and the result set does contain one row only |