Considering that someone earlier in this thread was specifically askingI didn't consider *removing* flexibility, but *adding* flexibility by allowing the function body after AS (which already is required to be right in front of the func def) not to be embraced by quotes.
to put LANGUAGE before the function body (apparently unaware that he
already could), I doubt we can get away with removing that flexibility.
But we're not talking about psql only (and \beginlit and \endlit are quite ugly sql keywords), and this should be a backend thing only (I hope you won't suggest that pgAdmin3 should be a frontend for psql :-)Initially, I didn't want to suggest an additional keyword like ENDFUNC or ENDAS, but now I do.
Once you say that, there's not a lot of distance to letting psql do it with \beginlit ... \endlit (or some other yet-to-be-chosen names).
I don't think that if both current and yet-to-be-decided syntax is allowed, a keyword embraced function definition would do any harm. In the (unlikely) case somebody uses that keyword inside the function, the parser will probably notice this instead of silently create a broken function.
Regards, Andreas
---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
