| From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
|---|---|
| To: | "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp>, "Venkatesan, Sekhar" <sekhar(dot)venkatesan(at)emc(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL: SQLSetPos fails with SetPos update return error. |
| Date: | 2016-05-19 01:57:25 |
| Message-ID: | 0A3221C70F24FB45833433255569204D1F577361@G01JPEXMBYT05 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Hello, Inoue-san, Sekhar,
Sorry for my late reply, I had to (and have still been) deal with my customer's trouble in the field, was away from work to go to hospital, etc. And I still don't understand psqlODBC well enough to keep up with Inoue-san.
From: Inoue, Hiroshi [mailto:h-inoue(at)dream(dot)email(dot)ne(dot)jp]
I don't think the cause of the SQLSetPos failure reported is partition row movement.
Yes, the cause is simply that the current SQLSetPos() implementation does not handle table inheritance. For example, if a table called "parent" has some child tables like "child1" and "child2", and only the child tables have actual rows, SQLSetPos() against the result set from "parent" issues UPDATE statements on "parent". It should execute UPDATE on the child tables instead.
Regards
Takayuki Tsunakawa
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tsunakawa, Takayuki | 2016-05-19 05:21:52 | Re: ADO CommandTimeout vs Postgres statement_timeout parameter |
| Previous Message | Adrian Klaver | 2016-05-18 23:32:16 | Re: ODBC driver support |