On 03/22/2016 02:43 PM, Joshua D. Drake wrote:
On 03/22/2016 01:35 PM, CS DBA wrote:
On 03/22/2016 02:23 PM, Joshua D. Drake wrote:
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.
Yes.. that's exactly the issue.
Because the parent table doesn't actually receive the insert, it is
returning correctly (if obnoxiously considering the circumstances). It
is known, expected behaviour.
Sincerely,
JD
Understood, was just wondering if there is a way to cause the child
table insert results to be returned to the ORM/Application instead of
the master/base table insert
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
