plpgsql syntax

I just want to bring up a point for discussion:
for the function definition is treated as a long string right now. Why
not add an additional token so that we don't have to write 10 single quotes.

for example
create function a_func() return integer as
......
end a_func

after as and before end a_func marks the definition body. Would this be
better than the ' '?
Kemin





************************************************************ **********
Proprietary or confidential information belonging to Ferring Holding SA or to one of its affiliated companies may be contained in the message. If you are not the addressee indicated in this message (or responsible for the delivery of the message to such person), please do not copy or deliver this message to anyone. In such case, please destroy this message and notify the sender by reply e-mail. Please advise the sender immediately if you or your employer do not consent to e-mail for messages of this kind. Opinions, conclusions and other information in this message represent the opinion of the sender and do not necessarily represent or reflect the views and opinions of Ferring.
************************************************************ **********


---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Re: plpgsql syntax

> for example
> create function a_func() return integer as
> .....
> end a_func
>
> after as and before end a_func marks the definition body. Would this be
> better than the ' '?

I guess having a parser that gave better error messages would be nice,
too.

Yasir

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

Re: plpgsql syntax

Kemin Zhou writes:
> I just want to bring up a point for discussion:
> for the function definition is treated as a long string right now. Why
> not add an additional token so that we don't have to write 10 single quotes.

Something's already been done about this for 8.0.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match