Re: Is replacing transactions with CTE a good idea? - Mailing list pgsql-general

From Rob Sargent
Subject Re: Is replacing transactions with CTE a good idea?
Date
Msg-id 02654280-7b22-1231-8de7-c74a1a62e426@gmail.com
Whole thread Raw
In response to Re: Is replacing transactions with CTE a good idea?  (Brian Dunavant <dunavant@gmail.com>)
Responses Re: Is replacing transactions with CTE a good idea?  (Ron <ronljohnsonjr@gmail.com>)
List pgsql-general
On 4/1/21 8:58 AM, Brian Dunavant wrote:
On Thu, Apr 1, 2021 at 10:49 AM Glen Huang <heyhgl@gmail.com> wrote:
If I decide to replace all my transaction code with CTE, will I shoot myself in the foot down the road?

I do this all the time and makes code way cleaner.   It's very straightforward with inserts queries.  When you deal with updates/deletes, things can be trickier.  I usually leave these in a transaction if there is any concern.

They can also be hard for future programmers that may not understand SQL.  Make sure you comment your queries for maintainability long term.  

I have yet to regret replacing a transaction with a CTE over the past decade.  YMMV
 
This must assume auto-commit mode where every single statement is "committed"?

pgsql-general by date:

Previous
From: Dave Cramer
Date:
Subject: Re: Is replacing transactions with CTE a good idea?
Next
From: Glen Huang
Date:
Subject: Re: Is replacing transactions with CTE a good idea?