Re: Is replacing transactions with CTE a good idea?
От | Ron |
---|---|
Тема | Re: Is replacing transactions with CTE a good idea? |
Дата | |
Msg-id | b6567fde-6617-2144-177e-857ce980dc4a@gmail.com обсуждение исходный текст |
Ответ на | Re: Is replacing transactions with CTE a good idea? (Rob Sargent <robjsargent@gmail.com>) |
Список | pgsql-general |
On 4/1/21 10:04 AM, Rob Sargent wrote:
That's the only way to explain an otherwise very puzzling question. OP must not do lots of DML in each transaction.
On 4/1/21 8:58 AM, Brian Dunavant wrote:This must assume auto-commit mode where every single statement is "committed"?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
That's the only way to explain an otherwise very puzzling question. OP must not do lots of DML in each transaction.
--
Angular momentum makes the world go 'round.
Angular momentum makes the world go 'round.
В списке pgsql-general по дате отправления: