Re: [partition table] python fetchall or fetchone function can not get the returning rows

From: Jasen Betts <jasen(at)xnet(dot)co(dot)nz>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: [partition table] python fetchall or fetchone function can not get the returning rows
Date: 2012-01-02 11:28:26
Message-ID: jds4cq$j7g$3@reversiblemaps.ath.cx
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2011-12-21, Xiaoning Xu <xixu(at)bcgsc(dot)ca> wrote:
> Hello,
>
> I have a problem concerning the partition table.
> When I store a record into one of the partition and use "RETURNING table_id" or "RETURNING *",
> I expect the same result when calling fetchall or fetchone function as not using partition.
> However, it simply returns nothing.

If you've got a before insert trigger there that does "return false" that's what
happens.

If you need returning to work, you could look at doing the
partitioning in a after insert trigger, deleteing from th main table
and inserting into the partition.

Else perhaps you can use a rule instead, have the rule run a function
and the function return the id.

--
⚂⚃ 100% natural

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Simon Windsor 2012-01-02 13:52:00 Re: Large Objects and and Vacuum
Previous Message John R Pierce 2012-01-02 11:17:55 Re: Large Objects and and Vacuum