Re: Is it considered good practice to use stored procedures for most tasks?

Do you have a "why" for your suggestion for not allowing direct table
access?

On Wed, Apr 17, 2019 at 4:32 PM Gaetano Mendola <mendola(at)gmail(dot)com> wrote:

> 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?
>>
>>
>>
>>