Skip to content

Change in autocommit in Django 1.6 results in UPDATE and INSERT operations to be unsaved. #3

@briandailey

Description

@briandailey

See notes for changes to transaction management in 1.6:

Before Django 1.6, autocommit was turned off, and it was emulated by forcing a commit after write operations in the ORM.

With this change, UPDATE operations are no longer applied as no explicit COMMIT is issued.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions