| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Joel Jacobson <joel(at)trustly(dot)com> |
| Cc: | Hannu Krosing <hannu(at)2ndquadrant(dot)com>, Marko Tiikkaja <marko(at)joh(dot)to>, Bruce Momjian <bruce(at)momjian(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PL/pgSQL 1.2 |
| Date: | 2014-09-04 15:18:03 |
| Message-ID: | CAFj8pRB=LmaV1tuN4pS9bPV=65_D1Z-VQ4RCjqbrDzr=5PtC_Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2014-09-04 17:16 GMT+02:00 Joel Jacobson <joel(at)trustly(dot)com>:
> > On 4 sep 2014, at 16:45, Hannu Krosing <hannu(at)2ndquadrant(dot)com> wrote:
> >
> > When looking from the other end of the problem, we are
> > using SELECT/INSERT/UPDATE/DELETE *SET statements* in pl/pgsql
> > when we really want scalars.
> >
> > My understanding is that one main drivers of starting this thread
> > was wanting also guaranteed SCALAR versions of these.
> >
> > And wanting them in a way that is easy to use.
>
> +1
>
> Thank you! I have been trying to explain this in multiple cryptic ways
> but failed. You just nailed it! That's *exactly* what I mean!
>
You just need a ISAM API for Postgres, That is all.
Pavel
>
> Thanks for clarifying!
>
> >
> >
> > Cheers
> >
> >
> > --
> > Hannu Krosing
> > PostgreSQL Consultant
> > Performance, Scalability and High Availability
> > 2ndQuadrant Nordic OÜ
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Jacobson | 2014-09-04 15:32:43 | Re: PL/pgSQL 1.2 |
| Previous Message | Pavel Stehule | 2014-09-04 15:17:01 | Re: PL/pgSQL 1.2 |