Re: Partitioning and ORM tools

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: CS DBA <cs_dba(at)consistentstate(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Partitioning and ORM tools
Date: 2016-03-22 20:43:02
Message-ID: 56F1AE56.1050201@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

>
>
>
>

--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Diogo Kiss 2016-03-22 20:48:17 Re: Unable to make postgres + pam_ldap to work agains LDAP server using ldaps schema
Previous Message CS DBA 2016-03-22 20:35:59 Re: Partitioning and ORM tools