Re: Bug? {? = CALL insert_page_segment (?, ?)} - Mailing list pgsql-odbc

From Nils Gösche
Subject Re: Bug? {? = CALL insert_page_segment (?, ?)}
Date
Msg-id 000601cffe77$6681ce20$33856a60$@de
Whole thread Raw
In response to Re: Bug? {? = CALL insert_page_segment (?, ?)}  ("Inoue, Hiroshi" <inoue@tpf.co.jp>)
Responses Re: Bug? {? = CALL insert_page_segment (?, ?)}
Re: Bug? {? = CALL insert_page_segment (?, ?)}
List pgsql-odbc
Hiroshi wrote:

> On 2014/11/12 2:08, Nils Gösche wrote:
> > Hi!
> >
> > I have a problem with newer versions of the ODBC driver. I made a
> > small testing example to reproduce the problem:
> >
> > The following code works fine with version 09.02.0100 of the driver.
> > With 09.03.0210, it crashes. With 09.03.0400, I get a strange
> > exception and error message.
>
> Please try to add ;parse=1 to your connection string or turn on the
> *Parse statements* option of your DSN.

This setting does not seem to make any difference.

Now I notice that the InvalidOperationException I am getting has an inner OdbcException, with the message:

"ERROR [08S01] No response from the backend"

On the server side, I still get:

2014-11-12 13:44:44 CET ERROR:  function insert_page_segment(unknown) does not exist at character 8
2014-11-12 13:44:44 CET HINT:  No function matches the given name and argument types. You might need to add explicit
typecasts. 
2014-11-12 13:44:44 CET STATEMENT:  SELECT insert_page_segment ($1, $2)
2014-11-12 13:44:44 CET FATAL:  invalid frontend message type 0

Regards,
--
Nils Gösche
"Don't ask for whom the <CTRL-G> tolls."




pgsql-odbc by date:

Previous
From: Christoph Berg
Date:
Subject: 09.03.0400 broken on 32bit
Next
From: Nils Gösche
Date:
Subject: Re: Bug? {? = CALL insert_page_segment (?, ?)}