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.