Rules and sequences

Поиск
Список
Период
Сортировка
От Ben Morrow
Тема Rules and sequences
Дата
Msg-id 20100526181620.GA54996@osiris.mauzo.dyndns.org
обсуждение исходный текст
Ответы Re: Rules and sequences  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-sql
I am trying to implement a fairly standard 'audit table' setup, but
using rules instead of triggers (since it should be more efficient).
However, I'm running into problems when one of the audited tables has a
'serial' column that is allowed to default:
   create table foo (id serial, bar text);   create table audit (ix bigserial, rec text);   create rule audit_insert as
oninsert to foo do also        insert into audit (rec) values ((new.*)::text);   insert into foo (bar) values ('baz');
select * from foo;        id | bar        ----+-----         1 | baz       (1 row)   select * from audit;        ix |
rec         ----+---------         1 | (2,baz)       (1 row)
 

I can see why this is happening (the rule is essentially a macro, so the
NEW expression gets expanded twice, including the nextval call, so the
sequence is incremented twice), but is there any way to prevent it? Some
way of 'materialising' the NEW row so it is just plain values rather
than a list of expressions?

Ben



В списке pgsql-sql по дате отправления:

Предыдущее
От: Michele Petrazzo - Unipex
Дата:
Сообщение: inner join and limit
Следующее
От: Rolando Edwards
Дата:
Сообщение: Re: inner join and limit