Jeff Eckermann wrote:
>Perhaps you are assuming that George is trying to
>update his views? But he's getting failure just on
>trying to select from them...
>
>
>
The problem is that, in order to ALLOW updating, the ODBC need to do
it's changes during the "Select" stage. This means that it doesn't
really matter whether you are actually doing any updates, so long as you
have not told the driver that you do not intend to do any.
>>the fields of the
>>view come from just one table, but will probably
>>fail miserably for
>>anything else. I also don't know how a query such as
>>"update <view>...."
>>will be accepted by postgresql.
>>
>>
>
>"create or replace view..." works on PostgreSQL
>versions 7.3 on, IIRC.
>"\dv viewname" to get view definition, "create or
>replace view ", copy and paste the view definition,
>edit to add what you want, hit enter and done. Easy!
>
>
>
update <table> doesn't change the table. update <table> changes values
inside the table. I don't think you can issue "update <view>" at all.
http://www.postgresql.org/docs/7.4/static/sql-update.html
>Thinking about this some more, this has to be an
>OpenOffice issue, because I have not seen this problem
>elsewhere, even with "updateable cursors" set to true
>in the driver. Not sure what changing that setting
>would do to the rest of the application.
>
>
OpenOffice has no way of knowing about these issues. It just uses an
ODBC interface.
Removing "updateable cursors" from the ODBC driver may actually solve
this problem, but this will, of course, make OpenOffice read only.
Shachar
--
Shachar Shemesh
Lingnu Open Systems Consulting
http://www.lingnu.com/
