Re: Problems with PGSQL ODBC drivers

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Harry Broomhall" <harry(dot)broomhall(at)uk(dot)easynet(dot)net>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Problems with PGSQL ODBC drivers
Date: 2003-01-10 15:23:57
Message-ID: EKEJJICOHDIEMGPNIFIJKEOFKEAA.Inoue@tpf.co.jp
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Please try the snapshot dll at http://w2422.nsk.ne.jp/~inoue/ .

regards,
Hiroshi Inoue

> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org]On Behalf Of Harry Broomhall
> Sent: Friday, January 10, 2003 8:48 PM
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] Problems with PGSQL ODBC drivers
>
>
> Henshall, Stuart - Design & Print writes:
> > So that MS Access can auto work out which field to use as a key
> I first of
> > all create a view as a table with primary key and then create a
> select rule.
>
>
> Thinking about this further, it occurs to me that if the driver
> routines for SQLSpecialColumns returned the actual Primary Key for a table
> (if it existed) rather than OID then Access may have the required hint?
>
> The sort of scheme I had in mind goes something like this:
>
> if (view)
> return SQL_NO_DATA
>
> else if (table) {
> if (primary key esists)
> return all elements of PK.
> else if (oid exists)
> return oid
> else
> return SQL_NO_DATA
> }
>
> Or am I way off-beam with this idea?
>
> Regards,
> Harry.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Harry Broomhall 2003-01-10 15:47:27 Re: Problems with PGSQL ODBC drivers
Previous Message Harry Broomhall 2003-01-10 11:47:33 Re: Problems with PGSQL ODBC drivers