On Tue, Mar 22, 2016 at 4:23 PM, Joshua D. Drake <jd@xxxxxxxxxxxxxxxxx> wrote:
>it's the fact that the number of rows inserted is returned as 0 - due to
>the fact that the rows are not in fact inserted in the parent table when
>configured as per the example in the docs.
On 03/22/2016 11:40 AM, CS DBA 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
Are you inserting via trigger from an insert into a parent table? That would do it.
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
>it's the fact that the number of rows inserted is returned as 0 - due to
>the fact that the rows are not in fact inserted in the parent table when
>configured as per the example in the docs.
Yes, you have declared a problem, but without providing actual detailed information (as previously requested), there is no way we can duplicate your problem to debug it and provide a solution.
To the best of my knowledge, telepathy and crystal ball options are not yet available and are not planned for future versions of PostgreSQL/
--
Melvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.![]()
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
