Re: Lowercase folding - simple patch? - Mailing list pgsql-odbc

From Dave Page
Subject Re: Lowercase folding - simple patch?
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC96B4@ratbert.vale-housing.co.uk
Whole thread Raw
In response to Lowercase folding - simple patch?  (agnewtj@netscape.net)
Responses Re: Lowercase folding - simple patch?  (Marko Ristola <Marko.Ristola@kolumbus.fi>)
List pgsql-odbc

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Marko Ristola
> Sent: 01 August 2005 17:28
> To: Merlin Moncure
> Cc: Eric E; pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] Lowercase folding - simple patch?
>
>
> Does somebody know, wether the following code is correct:
>
> odbcapi.c:
>
>
> RETCODE        SQL_API
> SQLColumns(HSTMT StatementHandle, ...)
> {
> ...
>
>         if (SC_is_lower_case(stmt, conn)) /* case-insensitive
> identifier */
>             ifallupper = FALSE;
>
> In above there is one hidden problem:
> SC_is_lower_case() is implemented as follows:
>
> statement.h:#define     SC_is_lower_case(a, b)
> (a->options.metadata_id,
> b->connInfo.lower_case_identifier)
>
>
> GCC compiler complaints (-Wall enabled) about the definition:
>
> odbcapi.c:140: warning: left-hand operand of comma expression
> has no effect
>
> So this means, that a->options.metadata_id is not used at
> all. Maybe the
> comma
> should be replaced with && or || ?

I *think* && is appropriate, however I'm too busy too look into this in
depth right now. Any chance you can confirm this?
(a->options.metadata_id is attribute SQL_ATTR_METADATA_ID btw).

Regards, Dave.

pgsql-odbc by date:

Previous
From: Marko Ristola
Date:
Subject: Re: IIS Postgres ASP ADO - Problem
Next
From: Eric E
Date:
Subject: Re: [BUGS] problem odbc 8.0 with EOModeler