Skip site navigation (1) Skip section navigation (2)

Re: Another bug with parse statements on

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: andrea(dot)aime(at)comune(dot)modena(dot)it
Cc: Postgres ODBC <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Another bug with parse statements on
Date: 2001-04-23 02:29:31
Message-ID: 3AE3938B.1DCFAD44@tpf.co.jp (view raw or flat)
Thread:
Lists: pgsql-odbc
Hi Andrea,

Andrea Aime wrote:
> 
> Hi everybody,
> I've just come up with another bug... my last solution was to
> apply my tiny bug fix on searchColInfo and keep "parse statements" = 1
> Unfortunately this breaks another query, I think because the parser
> has some problem with the "as" keyword... With "parse statements" = 1
> the following query, issued from VB (using ADO 2.6), fails:
> 
> 'SELECT min(classe) as minimo, max(classe) as massimo
> FROM tav974'
> (
>  is a carriage return...)
> 

What kind of errors do you see ?
I couldn't find any related ERRORs in your log.

regards,
Hiroshi Inoue

In response to

Responses

pgsql-odbc by date

Next:From: Andrea AimeDate: 2001-04-23 06:24:06
Subject: Re: Another bug with parse statements on
Previous:From: Rob YampolskyDate: 2001-04-21 02:40:35
Subject: Re: How to configure iodbc access to local postgres db?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group