From: David Hartwig <daveh@insightdist.com>
To: Sbragion Denis <infotecn@tin.it>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Odbc and Visual Basic
Date: Mon, 27 Apr 1998 12:54:08 -0400
Message-ID: <3544B82F.A48F95B6@insightdist.com> (raw)
References: <3.0.5.32.19980427102627.008acaa0@MBox.InfoTecna.com>
<3.0.5.32.19980427182218.008412d0@MBox.InfoTecna.com>
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:
> Hello,
>
> 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...
>
Attachments:vcard.vcf (text/x-vcard, 202B) download
begin: vcard
fn: David Hartwig
n: Hartwig;David
email;internet: daveh@insightdist.com
x-mozilla-cpt: ;0
x-mozilla-html: FALSE
version: 2.1
end: vcard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: daveh@insightdist.com, infotecn@tin.it
Subject: Re: [INTERFACES] Odbc and Visual Basic
In-Reply-To: <3544B82F.A48F95B6@insightdist.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox