Re: Partitioning and ORM tools

From: CS DBA <cs_dba(at)consistentstate(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Partitioning and ORM tools
Date: 2016-03-22 21:20:33
Message-ID: 56F1B721.5040504@consistentstate.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 03/22/2016 03:18 PM, Rob Sargent wrote:
>
>
> On 03/22/2016 03:00 PM, Joshua D. Drake wrote:
>> On 03/22/2016 01:50 PM, CS DBA wrote:
>>
>>> 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
>>
>> Insert into the child table directly based on the partition rules.
>>
>> JD
>>
>>
> I would think the ORM (as yet undefined) would want to think in terms
> of the parent table and not know about the physical schema details.
> Can the client not be written to check only for errors vs checking
> for non-zero inserts?
>
>
>
That was our first suggestion, they don;t want to make any app changes

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Melvin Davidson 2016-03-22 21:24:27 Re: Partitioning and ORM tools
Previous Message Rob Sargent 2016-03-22 21:18:55 Re: Partitioning and ORM tools