Re: [GENERAL] AW: [HACKERS] TRANSACTIONS
От | Peter Eisentraut |
---|---|
Тема | Re: [GENERAL] AW: [HACKERS] TRANSACTIONS |
Дата | |
Msg-id | Pine.GSO.4.02A.10002241713480.17421-100000@Hummer.DoCS.UU.SE обсуждение исходный текст |
Ответ на | Re: [GENERAL] AW: [HACKERS] TRANSACTIONS (Jose Soares <jose@sferacarta.com>) |
Список | pgsql-general |
On Thu, 24 Feb 2000, Jose Soares wrote: > NOTICE: (transaction aborted): all queries ignored until end of transaction block > > *ABORT STATE* > Why PostgreSQL doesn't make an implicit ROLLBACK instead of waitting for a > COMMIT/ROLLBACK ? The PostgreSQL transaction paradigm seems to be that if you explicitly start a transaction, you get to explicitly end it. This is of course at odds with SQL, but it seems internally consistent to me. I hope that one of these days we can offer the other behaviour as well. > Why PostgreSQL allows a COMMIT in this case ? Good question. I assume it doesn't actually commit though, does it? I think a CHECK_IF_ABORTED (sp?) before calling the commit utility routine would be appropriate. Anyone? -- Peter Eisentraut Sernanders vaeg 10:115 peter_e@gmx.net 75262 Uppsala http://yi.org/peter-e/ Sweden
В списке pgsql-general по дате отправления: