See Byron's posting on this subject. We are getting some interesting result
from our yet-to-be-posted hacks. The cool part is that, MS Access no longer
requests the user to tag the primary key at link time. The downside, though,
is that it has a higher potential for exposing a known bug in the backend's
optimizer. The bug has to with multipart keys and the large numbers of ANDs
and ORs generated in a single statement while browsing tables.
Sbragion Denis wrote:
> At 08.14 27/04/98 -0400, David Hartwig wrote:
> >Here is an excerpt from the soon to be published ODBC FAQ.
> >How do I get my application to recognize primary keys?
> >SQLPrimaryKeys() is implemented in the driver. As of the driver's
> release, however,
> Unfortunately VB 5.0 seems to ignore the SQLPrimaryKey() call and insists
> looking for a unique index. It was the first thing I tried when I saw the
> announce for the support of that call. I also know that the concept of
> Primary Key is different from the concept of Unique Index (though on most
> database system, including PostgreSQL, the Primary Key concept is
> implemented using unique indexes), and using the SQLPrimaryKey() call would
> be The Right Way To Do Things (tm), but as long as Microsoft doesn't
> understand it... I don't know what would have happened if the ODBC
> interface specification have come from someone else than Microsoft itself...
Description: text/x-vcard (204 bytes)
In response to
pgsql-interfaces by date
|Next:||From: Byron Nikolaidis||Date: 1998-04-27 19:05:11|
|Subject: New Driver and Unique Indexes|
|Previous:||From: Sbragion Denis||Date: 1998-04-27 16:29:03|
|Subject: Re: [INTERFACES] Odbc and Visual Basic|