Re: Partitioning and ORM tools - Mailing list pgsql-general

From CS DBA
Subject Re: Partitioning and ORM tools
Date
Msg-id 56F1B721.5040504@consistentstate.com
Whole thread Raw
In response to Re: Partitioning and ORM tools  (Rob Sargent <robjsargent@gmail.com>)
Responses Re: Partitioning and ORM tools  (Melvin Davidson <melvin6925@gmail.com>)
Re: Partitioning and ORM tools  (Adrian Klaver <adrian.klaver@aklaver.com>)
Re: Partitioning and ORM tools  (John R Pierce <pierce@hogranch.com>)
List 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




pgsql-general by date:

Previous
From: Rob Sargent
Date:
Subject: Re: Partitioning and ORM tools
Next
From: Melvin Davidson
Date:
Subject: Re: Partitioning and ORM tools