Folks,
Please find enclosed a patch that fixes the trigger example in plpgsql
(emp_stamp).
Cheers,
D
--
David Fetter [EMAIL PROTECTED] http://fetter.org/
phone: +1 510 893 6100 mobile: +1 415 235 3778
Remember to vote!
Index: doc/src/sgml/plpgsql.sgml
David Fetter [EMAIL PROTECTED] writes:
Please find enclosed a patch that fixes the trigger example in plpgsql
(emp_stamp).
Uh ... that example is not broken.
If we were going to change it, I'd favor current_timestamp over
either Postgres-ism.
regards, tom lane
On Thu, Oct 20, 2005 at 08:03:13PM -0400, Tom Lane wrote:
David Fetter [EMAIL PROTECTED] writes:
Please find enclosed a patch that fixes the trigger example in plpgsql
(emp_stamp).
Uh ... that example is not broken.
If we were going to change it, I'd favor current_timestamp over
either
On Thu, 2005-20-10 at 20:03 -0400, Tom Lane wrote:
If we were going to change it, I'd favor current_timestamp over
either Postgres-ism.
Committed.
-Neil
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire