Re: PERSISTANT PREPARE (another point of view) - Mailing list pgsql-sql

From Tom Lane
Subject Re: PERSISTANT PREPARE (another point of view)
Date
Msg-id 378.1215819761@sss.pgh.pa.us
Whole thread Raw
In response to PERSISTANT PREPARE (another point of view)  (Milan Oparnica <milan.opa@hotmail.com>)
Responses Re: PERSISTANT PREPARE (another point of view)  (Milan Oparnica <milan.opa@gmail.com>)
List pgsql-sql
Milan Oparnica <milan.opa@hotmail.com> writes:
> [ much snipped ]
> What could we gain by introducing a kind of global prepared statement area, is SIMPLICITY of DB DEVELOPMENT AND
MAINTENANCE.
> The idea is: LETS SEPARATE SQL STATEMENTS FROM APPLICATION CODE.

Most people around this project think that the best way to do that is to
push as much logic as you can into server-side stored procedures.  That
gives you every advantage that a persistent-prepared-statement feature
would offer, and more besides:

* you can push procedural logic, as well as SQL, out of the application

* you can improve performance by reducing the number of network round
trips needed to accomplish a multi-SQL-statement task
        regards, tom lane


pgsql-sql by date:

Previous
From: Milan Oparnica
Date:
Subject: PERSISTANT PREPARE (another point of view)
Next
From: Steve Midgley
Date:
Subject: Re: PERSISTANT PREPARE (another point of view)