Re: trigger compile problem

I certainly wouldn't.
I am wondering if somehow pgaccess left this out and I cut and paste d waht
pgaccess built. I'll check that in the morning.

The good news is my db absolutly screems now that I moved some processing
to
a trigger. No more reason to look at mysql which I was dreading.

thanks for all the good work Tom,
t.r. missner

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Tuesday, September 25, 2001 11:23 PM
To: Missner, T. R.
Cc: Jan Wieck; doug(at)wireboard(dot)com; pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] trigger compile problem

T(dot)R(dot)Missner(at)Level3(dot)com writes:
> It was the ; after END
> I feel like a tard.
> spent over 5 hours on this .

I've always wondered why plpgsql is so nitpickingly insistent on finding
a semicolon after the last END. Would anyone object if I made the
last semi optional?

regards, tom lane