Postgres Pro
Downloads
Home   >   mailing lists

Re: why semicolon after begin is not allowed in postgresql? - Mailing list pgsql-hackers

From AK
Subject Re: why semicolon after begin is not allowed in postgresql?
Date
Msg-id 1385412124750-5780216.post@n5.nabble.com
Whole thread Raw
In response to Re: why semicolon after begin is not allowed in postgresql?  (Kevin Grittner <kgrittn@ymail.com>)
Responses Re: why semicolon after begin is not allowed in postgresql?  (Andrew Dunstan <andrew@dunslane.net>)
Re: why semicolon after begin is not allowed in postgresql?  (David Johnston <polobo@yahoo.com>)
Re: why semicolon after begin is not allowed in postgresql?  (Kevin Grittner <kgrittn@ymail.com>)
Re: why semicolon after begin is not allowed in postgresql?  (Mark Kirkwood <mark.kirkwood@catalyst.net.nz>)
List pgsql-hackers
Tree view 
Kevin,

I do see your logic now, but this thing is a common mistake - it means that
this seems counter-intuitive to some people. What would happen if we applied
Occam's razor and just removed this rule?

All existing code would continue to work as is, and we would have one less
rule to memorize. That would make PostgreSql a slightly better product,
right?



--
View this message in context:
http://postgresql.1045698.n5.nabble.com/why-semicolon-after-begin-is-not-allowed-in-postgresql-tp5779905p5780216.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.

pgsql-hackers by date:

Previous
From: AK
Date:
Subject: Re: Why is UPDATE with column-list syntax not implemented
Next
From: Andres Freund
Date:
Subject: Re: Errors on missing pg_subtrans/ files with 9.3