From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Christoph Moench-Tegeder <cmt(at)burggraben(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: LYDB: What advice about stored procedures and other server side code? |
Date: | 2016-12-29 15:33:35 |
Message-ID: | cd647ab2-7bc0-f43d-354e-85d02aa39f2c@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 12/29/2016 02:12 AM, Christoph Moench-Tegeder wrote:
> ## Karsten Hilbert (Karsten(dot)Hilbert(at)gmx(dot)net):
>
>>> Many applications are not designed to have a "stable" database API.
>> It seems OP is arguing they should.
>
> Well, if the environment allows for that, fine. If not, well, duh.
Been following along and while there are several views there seems to be
one constant: "there should be a method to the madness". For a
particular situation a best try should be made to analyze what the
current and future needs are and plan a course of action that meets
those needs the best. This could be database-centric or app-centric. In
a perfect world this would be a non-biased decision, though I suspect it
tends to follow the inclinations/backgrounds of those involved in the
planning. In any case a defined course of action that is set out and
followed would seem to be better then arbitrarily bolting on
new/different methods on a whim.
>
> Regards,
> Christoph
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Gerhard Wiesinger | 2016-12-29 18:24:51 | Re: vacuumdb --analyze-only scans all pages? |
Previous Message | Tom Lane | 2016-12-29 15:10:21 | Re: vacuumdb --analyze-only scans all pages? |