| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Marko Tiikkaja <marko(at)joh(dot)to> |
| Cc: | Joel Jacobson <joel(at)trustly(dot)com>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, 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 08:56:45 |
| Message-ID: | CAFj8pRCjLzMZorVHGZNOaFAfWkisJDSThv3c8pX=tWEspH2ESQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2014-09-04 10:53 GMT+02:00 Marko Tiikkaja <marko(at)joh(dot)to>:
> On 9/4/14 10:42 AM, Pavel Stehule wrote:
>
>> 2014-09-04 10:06 GMT+02:00 Joel Jacobson <joel(at)trustly(dot)com>:
>>
>>> *) but there are probably equally who prefer to handle business logics
>>> outside the database
>>>
>>> It is maybe main difference between me and you. Usually I don't write
>> CRUD
>> applications, and I am not sure if plpgsql is good for CRUD.
>>
>> Mainly I would not to optimize plpgsql primary for CRUD.
>>
>
> I don't think providing syntax to support the CRUD-like use case would be
> "optimizing it primarily for CRUD". Changing how UPDATE and DELETE work by
> default would be, but that's not being suggested here (anymore).
>
I am strong in opinion so safe stored procedures should be verbose. It is
in contradiction to Joel direction.
I wrote a proposal, how to do more friendly but still enough verbose
Pavel
>
>
> .marko
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Jacobson | 2014-09-04 08:57:50 | Re: PL/pgSQL 1.2 |
| Previous Message | Marko Tiikkaja | 2014-09-04 08:53:05 | Re: PL/pgSQL 1.2 |