From: | Scott Mead <scott(dot)lists(at)enterprisedb(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-advocacy(at)postgresql(dot)org |
Subject: | Re: DRAFT beta release announcement |
Date: | 2010-04-28 13:37:06 |
Message-ID: | l2ld3ab2ec81004280637w9bd34a5cv64ae74fcea5a4406@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
On Tue, Apr 27, 2010 at 6:20 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 4/27/10 2:47 PM, Chris Browne wrote:
> > jd(at)commandprompt(dot)com ("Joshua D. Drake") writes:
> >>> * The DO() statement, allowing users to execute ad-hoc procedural
> statements
> >> DO() support, allowing for inline? execution of procedural statements.
> >>
> >> Not quite sure about this one. I don't like the word ad-hoc. Dynamic?
> >
> > Hmm. How about...
> >
> > DO() enables users to execute procedural statements without requiring
> > assigning function names.
> >
> > That's clearer, though a bit wordier.
>
> I'd really prefer something that fits into a bullet without wrapping.
>
+1 for anonymous blocks. It's a common term in the industry, and may raise
more eyebrows than 'ad-hoc' or 'dynamic'
--Scott
>
> --
> -- Josh Berkus
> PostgreSQL Experts Inc.
> http://www.pgexperts.com
>
> --
> Sent via pgsql-advocacy mailing list (pgsql-advocacy(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-advocacy
>
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2010-04-28 21:38:09 | Re: DRAFT beta release announcement |
Previous Message | Simon Riggs | 2010-04-28 09:52:12 | Re: DRAFT beta release announcement |