Re: Trigger question
От | Richard Huxton |
---|---|
Тема | Re: Trigger question |
Дата | |
Msg-id | 200401201905.46699.dev@archonet.com обсуждение исходный текст |
Ответ на | Re: Trigger question (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-performance |
On Tuesday 20 January 2004 16:42, Tom Lane wrote: > Harald Fuchs <hf118@protecting.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. -- Richard Huxton Archonet Ltd
В списке pgsql-performance по дате отправления: