On Tuesday 20 January 2004 16:42, Tom Lane wrote:
> Harald Fuchs <hf118(at)protecting(dot)net> writes:
> > Why? If the underlying table has a primary key, finding corresponding
> > pairs is trivial; if there isn't, it's impossible.
> Exactly. Nonetheless, the correspondence exists --- the UPDATE
> definitely updated some particular row of the OLD set into some
> particular one of the NEW set. If the trigger API makes it impossible
> to reconstruct the matchup, the API is broken.
Perhaps they should be cursors? The only sensible way I can think of working
with them would be:
1. count how many rows affected
2. step through one row at a time, doing something.
I suppose there might be cases where you'd want to GROUP BY... which would
mean you'd need some oid/row-id added to a "real" recordset.
In response to
pgsql-performance by date
|Next:||From: Orion Henry||Date: 2004-01-20 19:47:09|
|Subject: database profiling|
|Previous:||From: Tom Lane||Date: 2004-01-20 16:42:30|
|Subject: Re: Trigger question |