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.
In response to
pgsql-odbc by date
|Next:||From: Andrea Aime||Date: 2001-04-23 06:24:06|
|Subject: Re: Another bug with parse statements on|
|Previous:||From: Rob Yampolsky||Date: 2001-04-21 02:40:35|
|Subject: Re: How to configure iodbc access to local postgres db?|