Search Postgresql Archives

Re: Multi-Table Insert/Update Strategy - Use Functions/Procedures?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jan 27, 2016 at 6:24 PM, David G. Johnston <david.g.johnston@xxxxxxxxx> wrote:
On Wed, Jan 27, 2016 at 4:03 PM, Don Parris <parrisdc@xxxxxxxxx> wrote:

<snip>
 
​Parameter passing and variables are client-side considerations.  You haven't told us how you plan to execute the SQL.

​IMO the most straight-forward API is a function.  Whether you implement that function using a updating CTE or a sequence of separate SQL commands is up to you to decide and, if performance matters, benchmark.

Comparing a CTE and function in general doesn't really do much good.  There are many non-performance concerns involved and the specific usage pattern involved will matter greatly in determining overhead.

 
Thanks David, that makes sense.  My main front-end - at the moment - is LibreOffice Base.  With Base, I can probably just create forms using the underlying tables.  That said, I may also want to write a Python front-end, in which case I would prefer to let the database do the work it was designed to do.

Don
--
D.C. Parris, FMP, Linux+, ESL Certificate
Minister, Security/FM Coordinator, Free Software Advocate
http://dcparris.net/
GPG Key ID: F5E179BE

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux