Thanks, patch applied.
Regards, Dave
> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Chris Ingram
> Sent: 14 September 2005 21:33
> To: Merlin Moncure
> Cc: pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] PATCH: SQLTables and case sensitivity
>
> I've attached a patch for this bug which I've tested using Microsoft
> ODBC Test to verify that it fixes the problem I reported.
> Please let me
> know if I should send this to any other email list (such as pgsql-bugs
> or pgsql-patches) instead of this one. Thanks.
>
> --
> Chris Ingram
> Software Developer, Intellisync Corporation
> cingram@intellisync.com
> www.intellisync.com
>
> -----Original Message-----
> From: Merlin Moncure [mailto:merlin.moncure@rcsonline.com]
> Sent: Wednesday, September 14, 2005 3:39 PM
> To: Chris Ingram
> Cc: pgsql-odbc@postgresql.org
> Subject: RE: [ODBC] SQLTables and case sensitivity
>
> > I'm running PostgreSQL 8.0 with version 08.01.0003 of the
> psqlodbclibpq
> > ODBC driver on Microsoft Windows Server 2003. I've noticed that
> > PostgreSQL stores unquoted identifiers as all lower case internally.
> > With the ODBC catalog functions such as SQLTables, if I
> don't specify
> > the table name with all lower case, it will not find it.
> For example,
> > if I create a table:
>
> [...]
>
> > What is the chance that a fix for this case insensitive problem will
> be
> > made to the official PostgreSQL ODBC driver?
>
> IMO, 100% if you test it and it fixes the behavior you have
> noticed, and
> submit a patch. I remember looking at this a while back and the
> existing code looked bugged.
>
> Merlin
>
