tml#PLPGSQL-STATEMENTS-EXECUTING-DYN
but you need to use keyword "plpgsql" what is preferred language for stored
procedures in Postgres. I don't know why Google is thinking so ecpg is more
than plpgsql :(.
Regards
Pavel
>
> On Thu, 22 Jun 2017 at 12:37 Pavel Stehule
>
2017-06-22 10:00 GMT+02:00 Gerard Matthews :
> Here's an example. this code does not exec for me, I get syntax error. I
> have PG version 9.5
>
> DO $$
> BEGIN
>
> EXEC SQL BEGIN DECLARE SECTION;
> const char *stmt = "CREATE TABLE test1 (...);";
> EXEC SQL END DECLARE SECTION;
> EXEC SQL EXECUTE I
Hi
2017-06-21 10:39 GMT+02:00 :
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.6/static/plpgsql-statements.html
> Description:
>
> Your documentation although it seems straight forward actually never
> works.
>
> The dynamic sql s
Hi
2017-03-11 17:24 GMT+01:00 :
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/8.3/static/plpgsql-trigger.html
> Description:
>
> Toward the end of:
> https://www.postgresql.org/docs/8.3/static/plpgsql-trigger.html
>
> in definition
2014-10-08 21:25 GMT+02:00 Marti Raudsepp :
> On Thu, Sep 4, 2014 at 3:06 PM, Marko Tiikkaja wrote:
> > Just came across a broken example in the docs
>
> +1. New version works. I would slightly prefer adding an alias to the
> table:
>
> RETURN QUERY SELECT s.quantity, s.quantity * s.price FRO
2014/1/15 Bruce Momjian
> On Wed, Jan 15, 2014 at 04:55:11PM +0100, Pavel Stehule wrote:
> > The problem is that these are philosophical issues that are not
> normally
> > covered in our docs. What I have done is to add a mention of which
> > option is c
2014/1/15 Pavel Stehule
>
>
>
> 2014/1/15 Bruce Momjian
>
>> On Wed, Jan 15, 2014 at 11:07:29AM +0100, Pavel Stehule wrote:
>> > I thought you would say that. :-) I don't see how this detail
>> makes
>> > sense in the sections
2014/1/15 Bruce Momjian
> On Wed, Jan 15, 2014 at 11:07:29AM +0100, Pavel Stehule wrote:
> > I thought you would say that. :-) I don't see how this detail makes
> > sense in the sections related to the syntax usage, so I looked in the
> > section Porting
2014/1/14 Bruce Momjian
> On Mon, Jan 13, 2014 at 03:36:18PM +0100, Pavel Stehule wrote:
> > Agreed. I added a sentence in the first mention of GET DIAGNOSTICS,
> and
> > indicated it was generic for that command. What I also added was
> your
> > descri
2014/1/13 Bruce Momjian
> On Mon, Jan 13, 2014 at 06:10:24AM +0100, Pavel Stehule wrote:
> > I find the rules above so complex that I don't see how we can
> recommend
> > a best syntax. What I did in the patch I just posted was to put the
> > preferre
2014/1/13 Bruce Momjian
> On Sun, Jan 12, 2014 at 07:00:09AM +0100, Pavel Stehule wrote:
> > Comment updated. Patch attached.
> >
> >
> >
> > Still I am missing message about preferred syntax (or we should to
> enhance GET
> > DIAGNOSTICS doc about
2014/1/12 Bruce Momjian
> On Sat, Jan 11, 2014 at 10:06:27PM +0100, Pavel Stehule wrote:
> >
> >
> >
> > 2014/1/11 Tom Lane
> >
> > Bruce Momjian writes:
> > > Oh, I think you are right. I have reverted the patch. Attached is
> >
2014/1/12 Bruce Momjian
> On Sat, Jan 11, 2014 at 10:06:27PM +0100, Pavel Stehule wrote:
> >
> >
> >
> > 2014/1/11 Tom Lane
> >
> > Bruce Momjian writes:
> > > Oh, I think you are right. I have reverted the patch. Attached is
> >
2014/1/11 Tom Lane
> Bruce Momjian writes:
> > Oh, I think you are right. I have reverted the patch. Attached is
> > proposed documentation for '='.
>
> Meh. Variable initialization is only one of multiple cases (assignment,
> GET DIAGNOSTICS; maybe others, I've not examined the grammar). Al
is not better to be consistent in doc?
Im not aganst to documentation second syntax, but examples in doc should be
consistent
Dne 11. 1. 2014 19:52 "Tom Lane" napsal(a):
> Bruce Momjian writes:
> > On Wed, May 29, 2013 at 10:02:20AM +0200, Pavel Stehule wrote:
> >>
y similar
functionality - and printf is some like developer Esperanto. We
significantly reduced complexity of printf function and we modified basic
rules for usage in SQL, but some very typical rules - like format
placeholders, we share - we don't introduce own rules there.
Regards
Pave
Hello
remove undocumented syntax for assign statements in plpgsql doc examples
related to
http://www.postgresql.org/message-id/CAJ4CxLkBFNAAsWdz=CsDkU1nC0De60WO15de=auf6q1w9ds...@mail.gmail.com
thread
Regards
Pavel Stehule
plpgsql-assign.patch
Description: Binary data
--
Sent via pgsql
2013/5/3 Bruce Momjian
> On Fri, May 3, 2013 at 01:34:45PM -0400, Alvaro Herrera wrote:
> > Bruce Momjian wrote:
> > > I just noticed from the commit logs that Pavel's name is spelled Pavel
> > > Stěhule. That mark above the e is a caron, and is explained here:
> > >
> > > http://en.wikiped
Hello
Here is patch for Erwin Brandstetter RETURN QUERY example
Regards
Pavel Stehule
return_query_doc.patch
Description: Binary data
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
is indeterminate.
CONTEXT: PL/pgSQL function "foo_trig" line 3 at RAISE
so current text in documentation is not correct too.
Regards
Pavel Stehule
>
> Josh
>
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Hello
2011/5/6 Josh Kupershmidt :
> [Moving to -docs]
>
> On Mon, May 2, 2011 at 12:00 PM, Pavel Stehule
> wrote:
>> Hello
>>
>> one czech user reported a bug in documentation -
>> http://www.postgresql.org/docs/8.4/static/plpgsql-trigger.html
>>
e table value constructor.
Regards
Pavel Stehule
_
Emotikony a pozadi programu MSN Messenger ozivi vasi konverzaci.
http://messenger.msn.cz/
---(end of broadcast)---
TIP 5: don't forg
22 matches
Mail list logo
