Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: BUG #3587: EXECUTE and trigger problem [VASCL:A1226546842]
- From: Cyrus Downey <cdowney(at)pryermachine(dot)com>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-bugs(at)postgresql(dot)org
- Subject: Re: BUG #3587: EXECUTE and trigger problem [VASCL:A1226546842]
- Date: Thu, 30 Aug 2007 08:59:32 -0500
|
but the documentation does not say I shouldn't be able to do it.
Additionally, an alternate method (which was not included) using
temporary tables works fine. It fails when switching to the old record. thanks cyrus Tom Lane wrote: Cyrus Downey <cdowney(at)pryermachine(dot)com> writes: |
- References:
- BUG #3587: EXECUTE and trigger problem
- From: cyrus
- Re: BUG #3587: EXECUTE and trigger problem
- From: Alvaro Herrera
- Re: BUG #3587: EXECUTE and trigger problem [VASCL:A163D284A86]
- From: Cyrus Downey
- Re: BUG #3587: EXECUTE and trigger problem [VASCL:A163D284A86]
- From: Tom Lane
- BUG #3587: EXECUTE and trigger problem
- Prev by Date: Re: to_tsquery stack overflow
- Next by Date: Re: BUG #3589: /etc/init.d/postgresql reload doesn't reflect /etc/postgresql/postgresql.conf log_statement
- Previous by thread: Re: BUG #3587: EXECUTE and trigger problem [VASCL:A163D284A86]
- Next by thread: BUG #3588: coalesce not working in join
- Indexes: