From: | Zeugswetter Andreas IZ5 <Andreas(dot)Zeugswetter(at)telecom(dot)at> |
---|---|
To: | hackers(at)postgreSQL(dot)org |
Cc: | "'brook(at)trillium(dot)NMSU(dot)Edu'" <brook(at)trillium(dot)NMSU(dot)Edu> |
Subject: | AW: [HACKERS] rules bug? |
Date: | 1999-04-28 08:04:00 |
Message-ID: | 219F68D65015D011A8E000006F8590C60267B353@sdexcsrv1.f000.d0188.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> create rule surveys_ins as on insert to surveys
> do instead
> insert into survey_data (survey_date, name)
> select new.survey_date, new.name where not exists
> (select * from survey_data d where d.survey_date = new.survey_date
> and d.name = new.name);
>
Since this is a rewrite rule, the whole statement gets rewritten, thus
leading to different results, when one statement inserts many rows (insert
into ... select)
or one statement only inserts one row (insert ...).
The "problem" is visibility of data. The rows that have already been
inserted by this
same statement (insert ...select) are not visible to the restricting select.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 1999-04-28 08:38:44 | Re: [HACKERS] EGCS becomes GCC |
Previous Message | Dmitry Samersoff | 1999-04-28 07:54:04 | Re: [HACKERS] EGCS becomes GCC |