Re: Is replacing transactions with CTE a good idea?

> When you deal with updates/deletes, things can be trickier

Care to expand why they are tricker? I presume they run the risk of being referenced more than once?

> On Apr 1, 2021, at 10:58 PM, Brian Dunavant <dunavant(at)gmail(dot)com> wrote:
>
> 
>> On Thu, Apr 1, 2021 at 10:49 AM Glen Huang <heyhgl(at)gmail(dot)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
>