Re: savepoint improvements
От | Merlin Moncure |
---|---|
Тема | Re: savepoint improvements |
Дата | |
Msg-id | b42b73150701221049k16936df1m4fdbaf022274ae22@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: savepoint improvements (Martijn van Oosterhout <kleptog@svana.org>) |
Список | pgsql-hackers |
On 1/22/07, Martijn van Oosterhout <kleptog@svana.org> wrote: > I don't understand this either. Everything you can do with nested > transactions you can also do with savepoints, so I'm really not > understand what the limitations are? > > Actually, looking at the savepoint documentation, it looks like there > is no way to say: > > if transaction_state ok then > release X > else > rollback to X exactly. > Which is what a normal COMMIT does (sort of). This is very irritating > for scripting, so maybe a "COMMIT TO X" command would be auseful > addition? right. thats exactly what I want (more or less, there are a couple of different ways to do it, but this is perfectly acceptable). The on errors bit was just a froofy addition that distracted from the core problem. merlin
В списке pgsql-hackers по дате отправления: