Re: Problems with PGSQL ODBC drivers - Mailing list pgsql-odbc

From Henshall, Stuart - Design & Print
Subject Re: Problems with PGSQL ODBC drivers
Date
Msg-id E382B5D8EDE1D6118DBE0008C759BCD6116B5F@WCPEXCHANGE
Whole thread Raw
In response to Problems with PGSQL ODBC drivers  (Harry Broomhall <harry.broomhall@uk.easynet.net>)
Responses Re: Problems with PGSQL ODBC drivers
List pgsql-odbc

Harry Broomhall wrote:
> Henshall, Stuart - Design & Print writes:
>> Harry Broomhall wrote:
>>> Hiroshi Inoue writes:
>>> [Charset iso-2022-jp unsupported, filtering to ASCII...]
>>>>
>>>> Please try to turn off the *Updatable cursors* DSN option.
>>>
>>>   Thank you for your quick response.
>>>
>>>   I have tried your suggestion with no success!  :-(
>>>
>>>   The problem is as before.
>>>
>>>   (Note - I tried previously to reply, but the 'From:' header line
>>> wasn't set for the list, and the remote mailer had some error.)
>>>
>>>   Regards,
>>>      Harry.
>>>
>> 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.
>
>
>    Thanks for your comments.  I wasn't aware particularly of the
> 'Create Rule' command, probably because it isn't in the standard!
>
>    I note the manual suggests that using 'create view' is better style
> than creating a table and select rule!  <grin>

True, but this way you can specify a primary key for your view which some things seem to like (eg MS Access). It is however a little naughty :)

>
>> A similar thing may stop Excel trying to choose oid as primary key.
>> This is assuming that you've already made sure that its not showing
>> the OID column
>
>   Er - I thought that views (created by 'CREATE VIEW') didn't have
> OIDs anyway?  So it hasn't got one to show?
>
>> and isn't set to use it as a fake index.
>
>   Can you expand on that please?  I'm not sure what you mean here.
>
>   Regards,
>       Harry.
>
>

You're correct about views shouldn't have OIDs, but I was wondering if the ODBC datasource was set to use OIDs with fake indexes (page 2 of the datasource advance options) it might be picking that up as a primary key; Alternativly this might be totaly irrelevant :/

- Stuart

DISCLAIMER:The information in this message is confidential and may be legally privileged. It is intended solely for the addressee.  Access to this message by anyone else is unauthorised.  If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful.  Please immediately contact the sender if you have received this message in error. Thank you.

pgsql-odbc by date:

Previous
From: Harry Broomhall
Date:
Subject: Re: Problems with PGSQL ODBC drivers
Next
From: Harry Broomhall
Date:
Subject: Re: Problems with PGSQL ODBC drivers