Re: DatabaseWrapper.needs_rollback and transaction.rollback()

I created an issue for this https://code.djangoproject.com/ticket/27504 , and created a pull request as well: https://github.com/django/django/pull/7577. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To

Re: DatabaseWrapper.needs_rollback and transaction.rollback()

Re fixing transaction.rollback: What would be the preferred way to fix this? I haven't personally tested it (a coworker has and reports that it doesn't work), but BaseDatabaseWrapper.set_rollback requires that in_atomic_block be True when set_rollback is called, which is not the case in this ex

DatabaseWrapper.needs_rollback and transaction.rollback()

After a validationError occurs, why is the transaction considered dirty, blocking all db reads/writes? In this example: https://bitbucket.org/marky1991/django-test/raw/59c9ff89e4b12b4a831c36171139cb022735201b/test1.py , I don't really expect a TransactionManagementError at all, as the failure

Re: Contenttypes.GenericForeignKey Docs Addition

I'm not sure if my patch is sufficiently clear (it's only two words), but I've created a patch and ticket here . -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group a

Contenttypes.GenericForeignKey Docs Addition

Could it be mentioned that GenericForeignKey fields can't be accessed in forms in the docs? Without stackoverflow, I would've probably never figured this out. When you try to access it through the form, all you get is a FieldError saying that the model doesn't even have the field you're looking

Support Negative Indexing on QuerySets

In this support ticket (https://code.djangoproject.com/ticket/13089), the original closer said "This is a long-standing explicit design decision in the ORM, and so gets a wontfix...". What is the reasoning behind this? Why is negative indexing of querysets disallowed? Thanks! -- You received