From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
---|---|
To: | David Hedberg <david(dot)hedberg(at)gmail(dot)com>, <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: [PATCH] Return the correct column names in SQLTables |
Date: | 2014-09-23 09:46:40 |
Message-ID: | 54214180.90807@vmware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
On 08/09/2014 07:29 PM, David Hedberg wrote:
> As noted in bug #1007689, the column names returned from SQLTables
> differs between ODBCv2 and ODBCv3.
Yep, we should fix that.
> This patch was needed to be able to
> list the tables when trying to import data in Excel 2010/PowerPivot.
Hmm. According to the ODBC documentation on SQLTables:
"The following columns have been renamed for ODBC 3.x. The column name
changes do not affect backward compatibility because applications bind
by column number."
So, arguably this is a bug in Excel/PowerPivot, if it's binding by
column name rather than number. But it doesn't really matter, we should
fix the column names anyway.
> A somewhat unrelated question:
> There is one more "fix" needed to get the import of data in PowerPivot
> working properly, and that is because PowerPivot insists on creating
> the query with mssql-style quotes. (select [schema].[table].* instead
> of select "schema"."table".* ..).
Ugh. How does that work with any other ODBC driver than MS SQL Server?
- Heikki
From | Date | Subject | |
---|---|---|---|
Next Message | David Hedberg | 2014-09-23 10:46:31 | Re: [PATCH] Return the correct column names in SQLTables |
Previous Message | David Hedberg | 2014-09-22 20:40:04 | Re: [PATCH] Return the correct column names in SQLTables |