From: | Gaetano Mendola <mendola(at)gmail(dot)com> |
---|---|
To: | Simon Connah <scopensource(at)gmail(dot)com> |
Cc: | pgsql-novice(at)lists(dot)postgresql(dot)org |
Subject: | Re: Is it considered good practice to use stored procedures for most tasks? |
Date: | 2019-04-17 20:32:25 |
Message-ID: | CAJycT5rVL=Q8C-2J-iLKca0QQd_FgdA4RqGkLW8sH5OcKWUtGA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
For sure do not allow your application to touch directly tables, use views
and sp, lately I'm abandoning views for table functions.
On Wed, Apr 17, 2019, 21:02 Simon Connah <scopensource(at)gmail(dot)com> wrote:
> Hi,
>
> I'm about to build a website using PostgreSQL and for the first time I
> am not going to be using an ORM. I want to do it manually because I want
> to take the time to learn to use PostgreSQL properly on its own. The
> question is should I use stored procedures for the majority of the
> database operations or should I just use ad hoc queries as and when I
> need them? The advantage I can see for stored procedures is that you can
> do complex queries just by calling a single function rather than having
> to make multiple queries to get the result that you need. Plus it keeps
> the majority of data handling code at the database level rather than in
> the application itself.
>
> I was wondering what the consensus was for this? Should I try and use
> stored procedures as much as possible or should I only use them for
> specific types of tasks?
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Horn | 2019-04-17 23:04:33 | Re: Is it considered good practice to use stored procedures for most tasks? |
Previous Message | Simon Connah | 2019-04-17 19:02:06 | Is it considered good practice to use stored procedures for most tasks? |