Subject: Re: proposal: schema variables
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
References: 
 <CAFj8pRDY+m9OOxfO10R7J0PAkCCauM-TweaTrdsrsLGMb1VbEQ@mail.gmail.com>
 <20171026220732.GI4496@localhost>
 <CAFj8pRAemkdaDuoRQzrhs2GU59Bb_yHuquJC6nyrwGHfVdLuLw@mail.gmail.com>
 <1509399760322-0.post@n3.nabble.com>
 <CAFj8pRC3jq38zpNRJjQepkQKogfKC=0teb4OviZ7RwZ4je8ymQ@mail.gmail.com>
 <5665be80-1772-4998-8dbc-3bd071c0d9ad@rielau.com>
 <CAFj8pRB9YEzD_-qno8Y2Xj08f4gu2LYJFBd1QDW82EKPW-vmsQ@mail.gmail.com>
 <1509485317393-0.post@n3.nabble.com>
 <CAFj8pRAnkj68ORyU7d3CtUER4-=c3oD0eU8=OLjA2UFv3orx2A@mail.gmail.com>
From: Gilles Darold <gilles.darold@dalibo.com>
Message-ID: <f6bd1e6f-80a6-2bb8-dd7e-8a692ce21cdf@dalibo.com>
Date: Wed, 1 Nov 2017 23:13:47 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: 
 <CAFj8pRAnkj68ORyU7d3CtUER4-=c3oD0eU8=OLjA2UFv3orx2A@mail.gmail.com>
Content-Type: multipart/alternative;
 boundary="------------CB2316872747386A52B5D82E"
Content-Language: en-US
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

This is a multi-part message in MIME format.
--------------CB2316872747386A52B5D82E
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Le 01/11/2017 =C3=A0 05:15, Pavel Stehule a =C3=A9crit=C2=A0:
>
>
> 2017-10-31 22:28 GMT+01:00 srielau <serge@rielau.com
> <mailto:serge@rielau.com>>:
>
>     Pavel,
>
>     There is no
>     DECLARE TEMP CURSOR
>     or
>     DECLARE TEMP variable in PLpgSQL
>     and
>
>
> sure .. DECLARE TEMP has no sense, I talked about similarity DECLARE
> and CREATE TEMP
>
>
>     CREATE TEMP TABLE has a different meaning from what I understand yo=
u
>     envision for variables.
>
>     But maybe I'm mistaken. Your original post did not describe the ent=
ire
>     syntax:
>     CREATE [TEMP] VARIABLE [IF NOT EXISTS] name AS type
>     =C2=A0 [ DEFAULT expression ] [[NOT] NULL]
>     =C2=A0 [ ON TRANSACTION END { RESET | DROP } ]
>     =C2=A0 [ { VOLATILE | STABLE } ];
>
>     Especially the TEMP is not spelled out and how its presence affects=
 or
>     doesn't ON TRANSACTION END.
>     So may be if you elaborate I understand where you are coming from.
>
>
> TEMP has same functionality (and implementation) like our temp tables
> - so at session end the temp variables are destroyed, but it can be
> assigned to transaction.

Oh ok, I understand thanks for the precision.

--=20
Gilles Darold
Consultant PostgreSQL
http://dalibo.com - http://dalibo.org


--------------CB2316872747386A52B5D82E
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Le 01/11/2017 à 05:15, Pavel Stehule a
      écrit :<br>
    </div>
    <blockquote type="cite"
cite="mid:CAFj8pRAnkj68ORyU7d3CtUER4-=c3oD0eU8=OLjA2UFv3orx2A@mail.gmail.com">
      <div dir="ltr"><br>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">2017-10-31 22:28 GMT+01:00 srielau <span
              dir="ltr">&lt;<a href="mailto:serge@rielau.com"
                target="_blank" moz-do-not-send="true">serge@rielau.com</a>&gt;</span>:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">Pavel,<br>
              <br>
              There is no<br>
              DECLARE TEMP CURSOR<br>
              or<br>
              DECLARE TEMP variable in PLpgSQL<br>
              and<br>
            </blockquote>
            <div><br>
            </div>
            <div>sure .. DECLARE TEMP has no sense, I talked about
              similarity DECLARE and CREATE TEMP<br>
            </div>
            <div><br>
            </div>
            <div> <br>
            </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              CREATE TEMP TABLE has a different meaning from what I
              understand you<br>
              envision for variables.<br>
              <br>
              But maybe I'm mistaken. Your original post did not
              describe the entire<br>
              syntax:<br>
              <span class="">CREATE [TEMP] VARIABLE [IF NOT EXISTS] name
                AS type<br>
                  [ DEFAULT expression ] [[NOT] NULL]<br>
                  [ ON TRANSACTION END { RESET | DROP } ]<br>
                  [ { VOLATILE | STABLE } ];<br>
                <br>
              </span>Especially the TEMP is not spelled out and how its
              presence affects or<br>
              doesn't ON TRANSACTION END.<br>
              So may be if you elaborate I understand where you are
              coming from.<br>
            </blockquote>
            <div><br>
            </div>
            <div>TEMP has same functionality (and implementation) like
              our temp tables - so at session end the temp variables are
              destroyed, but it can be assigned to transaction.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Oh ok, I understand thanks for the precision.<br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Gilles Darold
Consultant PostgreSQL
<a class="moz-txt-link-freetext" href="http://dalibo.com">http://dalibo.com</a> - <a class="moz-txt-link-freetext" href="http://dalibo.org">http://dalibo.org</a>
</pre>
  </body>
</html>

--------------CB2316872747386A52B5D82E--