From: | Chris Travers <chris(dot)travers(at)gmail(dot)com> |
---|---|
To: | CS DBA <cs_dba(at)consistentstate(dot)com> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Partitioning and ORM tools |
Date: | 2016-03-23 08:39:32 |
Message-ID: | CAKt_ZfvSNKp3rWA26313JO1H_QbVGmuPHeU1rEeL1qSyf8OLXw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)consistentstate(dot)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(at)postgresql(dot)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.
http://www.efficito.com/learn_more
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Travers | 2016-03-23 08:48:20 | Re: Partitioning and ORM tools |
Previous Message | John R Pierce | 2016-03-23 01:49:37 | Re: Partitioning and ORM tools |