The fix was to stop the driver incorrectly reporting we support 4 part names, which we definitely do not, and most likely never will (because of the way a single backend connects to a single database).
From: "Austin Foxley"<afoxley(at)bluetooth(dot)com>
Sent: 27/08/05 07:03:02
Subject: [ODBC] Four part names
I've noticed that the current release of the driver doesn't support four
part names. According to some earlier postings earlier this month, it
sounds like Dave might have fixed this, but there has been no release
since his commit.
Can someone confirm whether this indeed has been fixed as I can't get
the current CVS to work.
I've been able to use MSSQL to create a linked server through this
driver, and have been able to do simple selects with OPENQUERY, but to
really make this usable, four part name support would be really nice.
Thanks a lot. This driver will be a life-saver!
Bluetooth SIG, Inc.
pgsql-odbc by date
|Next:||From: Alejandro D. Burne||Date: 2005-08-28 20:49:24|
|Subject: Re: Trouble with encoding again|
|Previous:||From: Lothar Behrens||Date: 2005-08-27 05:32:13|
|Subject: SQL query with no result set but inserting possible ?|