Re: Partitioning and ORM tools - Mailing list pgsql-general

From Chris Travers
Subject Re: Partitioning and ORM tools
Date
Msg-id CAKt_ZfvSNKp3rWA26313JO1H_QbVGmuPHeU1rEeL1qSyf8OLXw@mail.gmail.com
Whole thread Raw
In response to Partitioning and ORM tools  (CS DBA <cs_dba@consistentstate.com>)
Responses Re: Partitioning and ORM tools  (Chris Travers <chris.travers@gmail.com>)
List pgsql-general
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@consistentstate.com> 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@postgresql.org)
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.

pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: Partitioning and ORM tools
Next
From: Chris Travers
Date:
Subject: Re: Partitioning and ORM tools