Calling any Oracle developer (Matt Boersma?, Ian Kelly?), I see that the Oracle backend has had savepoint support since [10022] in March.
I'd like to understand whether this was done: a) simply to add the feature (which is good!) b) "by necessity" to be able to perform savepoint rollback when a transaction gets broken by IntegrityErrors Savepoints were first implemented in Postgresql with [8314] last August, and were implemented for reason (b). Once a Postgresql transaction experiences an IntegrityError, it refuses all further commands with "current transaction is aborted, queries ignored until end of transaction block" until it has been rolled back to a prior savepoint (see http://groups.google.com/group/django-developers/browse_thread/thread/c87cf2d97478c068/ , http://docs.djangoproject.com/en/dev/topics/db/transactions/#handling-exceptions-within-postgresql-transactions) Are savepoints needed for this reason (b) in Oracle too, or are they simply there as a feature for users? i.e. does an Oracle transaction continue to function without savepoint rollback after an IntegrityError? Thanks, Richard. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
