#13817: Error message when cache.set has trouble. ------------------------------------------+--------------------------------- Reporter: ezimir | Owner: nobody Status: new | Milestone: Component: Database layer (models, ORM) | Version: 1.1-beta-1 Keywords: | Stage: Unreviewed Has_patch: 0 | ------------------------------------------+--------------------------------- I am using low-level cache in my app, there were some cases when the `cache.set` method reported the `TransactionManagementError: This code isn't under transaction management` error, because (I guessed) that there is some underlying DB execution error.
I managed to find out what that original error was (with PDB) (and solve the problem): `OperationalError: (1153, "Got a packet bigger than 'max_allowed_packet' bytes")` Now, is there a way to retrieve the original error from code? Is there a way to tell Django not to try to rollback that unsuccessful query? Is it a bug (i.e. Django shouldn't try to rollback code that is not under transaction management)? Is it a version specific problem? django.VERSION is: `(1, 1, 1, 'final', 0)` django.get_version() says: 1.1.1 SVN-865 Thank you for your time. -- Ticket URL: <http://code.djangoproject.com/ticket/13817> Django <http://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.
