On Fri, 10 Jun 2011 12:25:25 +0200, André Knappstein, Controlling
<Knappstein@...> wrote:

> Your trigger runs when the records have been inserted, but the insert is
> not yet committed.

The trigger runs for every individual INSERT into table A, and that is at a
time when the inserts into child tables B and C have not yet occurred. So
it is to be expected that there is nothing to see.

> It is possible to configure transactions to read uncommitted inserts, but
> that would be by far too hot to handle for me :)

In general a transaction will see its own inserted data, just not that of
other uncommitted transactions.