Re: Bug#108286: case sensitivity in column names

"Oliver Elphick" <olly@lfix.co.uk> writes:

> You must have created the table in PostgreSQL using quoted names for
> the column (but not for the table, since PostgreSQL matches
> FaultAttributes with faultattributes).

Yep.

> Why not dump and recreate your database, but edit the dumpfile to
> remove the double-quotes and thus force the names to become
> case-insensitive?  Then it won't matter that OleDB is sending garbage.

I've tried to pass double quotes through OleDB, but it doesn't seem to
work.  On the other hand, double quotes do work with SQL
statements through (I assume) ODBC.

So to sum up,
        recreated database without quotes (changing a few names that
                clashed),
and
        changing direct SQL queries to not quote names

did the trick (mostly).

What remains of the wishlist item is, I guess, a wish for a case sensitive
OleDB driver.  Thanks for your help in clarifying things!

-kzm
--
If I haven't seen further, it is by standing in the footprints of giants