| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Petr Jelinek <petr(at)2ndquadrant(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: mogrify and indent features for jsonb |
| Date: | 2015-04-29 17:19:48 |
| Message-ID: | CA+Tgmoa1Z+6Gnqf_8RFeOnud5jPBv-MG_EVKpKCMEfjQQv02Zg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Apr 27, 2015 at 6:41 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> There's one exception I, at least, have to this rule, namely when there's a
> corresponding compound if or else. I personally find this unaesthetic to put
> it mildly:
>
> if (condition)
> statement;
> else
> {
> block of statements;
> }
Hmm, I don't dislike that style. If somebody submitted a patch with
braces around the lone statement, I would remove them before
committing.
<ducks>
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2015-04-29 17:34:51 | Re: Feedback on getting rid of VACUUM FULL |
| Previous Message | Robert Haas | 2015-04-29 17:18:17 | Re: Reducing tuple overhead |