Use a view with a DO INSTEAD trigger. That will allow you to return the tuple properly.
On Tue, Mar 22, 2016 at 7:40 PM, CS DBA <cs_dba@xxxxxxxxxxxxxxxxxxx> wrote:
Hi All;
we setup partitioning for a large table but had to back off because the return status (i.e: "INSERT 0 1") returns "INSERT 0 0" when inserting into the partitioned table which causes the ORM tool to assume the insert inserted 0 rows. Is there a standard / best practices work around for this?
Thanks in advance
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
--
Best Wishes,
Chris Travers
Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor lock-in.
