| From: | Grzegorz Jaskiewicz <gj(at)pointblue(dot)com(dot)pl> |
|---|---|
| To: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
| Cc: | Emmanuel Cecchet <manu(at)frogthinker(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fwd: [PATCHES] Auto Partitioning Patch - WIP version 1 |
| Date: | 2008-12-16 17:17:02 |
| Message-ID: | C2733311-4B26-4F06-B995-0D4896142D95@pointblue.com.pl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On 2008-12-16, at 07:58, ITAGAKI Takahiro wrote:
>
>
>>> server says "INSERT 0 row" though rows are inserted into child
>>> tables.
>> Technically this is correct since 0 rows were inserted in the parent
>> table.
>
> Yes, but users expect non-0 result normally. Some O/R mapping tools
> also checks the result exactly and raises errors (it could be turned
> off, but default is on).
this is a general problem with triggers on inserts/updates/deletes. To
be honest, I would love to see someone fixing it in 8.4, cos it is
quite annoying - that developer is unable to figure out number of rows
affected - just because there's trigger on that table.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2008-12-16 17:29:33 | Re: DTrace probes patch |
| Previous Message | Bruce Momjian | 2008-12-16 16:54:46 | Re: DROP ROLE dependency tracking ... |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-12-18 01:31:21 | Re: [PATCHES] Infrastructure changes for recovery (v8) |
| Previous Message | Emmanuel Cecchet | 2008-12-16 08:19:31 | Re: Fwd: [PATCHES] Auto Partitioning Patch - WIP version 1 |