Message-ID: <3889DD8D.32ACABD8@home.com>
Date: Sat, 22 Jan 2000 11:40:46 -0500
From: Byron Nikolaidis <byron.nikolaidis@home.com>
Organization: @Home Network
MIME-Version: 1.0
To: Jose Soares <jose@sferacarta.com>
CC: interfaces <pgsql-interfaces@postgreSQL.org>,
	hackers <pgsql-hackers@postgreSQL.org>
Subject: Re: [INTERFACES] Re: ODBC drive strange behavior
References: <38881F35.CAA49A56@sferacarta.com>
	<38881FC3.D34B1BEC@sferacarta.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit


Jose Soares wrote:
> 
> Sorry I forgot to send the attachement  :)
> 
> Jose Soares wrote:
> 
> > Please help!
> >
> > The PSQLODBC aborts a transaction with a strange error while execute a
> > legal query.
> > The message is:
> >
> > "Could not begin a transaction; unexpected protocol character from
> > backend (sen_query) (#1)"
> >
> > I tried the same query with psql client and it works with no problems.
> >
> > Does anyone know what this message means ?
> >
> > My configuration:
> >
> > Data base server: PostgreSQL v6.5.2
> > OS server: Linux 2.0.37 (Debian)
> > Win Client: M$_Access95
> > PsqlODBC v6.40.0006
> > log file attached.
> >
> > Any help would be very apreciated.
> >
> > José
> 
>   ------------------------------------------------------------------------
>                     Name: LOG_ERROR.log
>    LOG_ERROR.log    Type: Text Document (application/x-unknown-content-type-txtfile)
>                 Encoding: base64


The error means the driver didn't receive the expected response
character from the backend.  For queries, the expected response would be
something like:

'T': results are coming (this one is the most likely expected)
'C': no tuples produced
'Z': ready for new query (in >= postgres 6.4 only).
'I': empty query produces this response
'N': notice
'E': error


In your case, the query begins:  (SELECT "figure"."azienda" 

It might be the extra parenthesis around the query ?  Try removing
them.  If that's not it, try making the query really short, just as an
experiment.  Also, using the wrong protocol with the backend can make
this happen.

Byron