From: | Harry Broomhall <harry(dot)broomhall(at)uk(dot)easynet(dot)net> |
---|---|
To: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: Problems with PGSQL ODBC drivers |
Date: | 2003-01-10 11:47:33 |
Message-ID: | 200301101147.LAA78391@haeb.noc.uk.easynet.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2003-01-10 15:23:57 | Re: Problems with PGSQL ODBC drivers |
Previous Message | Steven Sluter | 2003-01-09 21:43:54 | Insert path fails |