Hi Takayuki/ Inoue,
When partition is enabled in my application and I change the partitioning key in the table to save the new data into another partition, I get error like this:
ERROR: new row for relation "testpart_s" violates check constraint " p1_testpart12_s"
I enabled constraint_exclusion in postgresql.conf.
I followed the document you shared to enable row movement across partitions by writing triggers on partition tables. It works up to a point but not confident it will work for all use-cases.
If this can be fixed in the odbc driver itself, it would be better. Let me know your thoughts on this.
Thanks,
Sekhar
From: Tsunakawa, Takayuki [mailto:tsunakawa.takay@jp.fujitsu.com]
Sent: Monday, May 23, 2016 1:18 PM
To: Venkatesan, Sekhar
Cc: Inoue, Hiroshi; Adrian Klaver; Joshua D. Drake; pgsql-odbc@postgresql.org
Subject: RE: [ODBC] PostgreSQL: SQLSetPos fails with SetPos update return error.
From: pgsql-odbc-owner@postgresql.org [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Venkatesan, Sekhar
The latest driver provided resolves the “SetPos update” error that you guys mentioned. Thanks for the fix.
That's good news.
Is the fix provided an official and certified one? Can you also provide the fix for Linux?
Inoue-san is the only committer now and he will decide that.
There is one another issue regarding partition’s automatic row movement with regards to partitioning key change. This is not fixed.
Let me know if it is feasible to fix that as well.
As Inoue-san and I mentioned before, automatic row movement seems to have nothing to do with your problem. Could you elaborate your test case which fails?
Regards
Takayuki Tsunakawa
