Folks,

Please find enclosed a patch that fixes the trigger example in plpgsql
(emp_stamp).

Cheers,
D
--
David Fetter david@fetter.org http://fetter.org/
phone: +1 510 893 6100 mobile: +1 415 235 3778

Remember to vote!


---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

David Fetter <david@fetter.org> 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

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

On Thu, Oct 20, 2005 at 08:03:13PM -0400, Tom Lane wrote:
> David Fetter <david@fetter.org> 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.

CURRENT_TIMESTAMP works. Shall I resend?

Cheers,
D
--
David Fetter david@fetter.org http://fetter.org/
phone: +1 510 893 6100 mobile: +1 415 235 3778

Remember to vote!

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

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 to
choose an index scan if your joining column's datatypes do not
match