According to Microsoft:
Attribute SQL_ATTR_METADATA_ID:
SQL_TRUE means, that table names and table columns are case insensitive.
SQL_FALSE means, that table names and table columns are case sensitive.
So, with this attribute, Microsoft Excel might give a hint wether the table
names are supposed to be handled as case sensitive (SQL_FALSE) or case
insensitive (SQL_TRUE).
It seems, that the lower case setting can be forced via ODBC config
via "lower_case_identifier" variable.
Alternatively the program (Excel) can activate it when needed
via SQL_ATTR_METADATA_ID attribute.
One Untested Solution into the Problem:
SC_is_lower_case(): (metadata_id || lower_case_identifier)
This way the case insensitivity can be either activated/deactivated
with ODBC API function calls,
or forced via Windows ODBC Driver setting regardless
what Excel wants.
The bug is now, that only the ODBC Driver setting is used under the
CVS HEAD psqlodbc.
I don't know, wether the newest stable
psqlodbc works with the ODBC Driver setting either, because that feature
has been fixed with the looong sprintf() with about 70 arguments.
Marko Ristola
Dave Page wrote:
>
>
>
>
>>
>>
>
>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.
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: explain analyze is your friend
>
>
