Changes between Initial Version and Version 1 of Ticket #37368, comment 6


Ignore:
Timestamp:
Oct 9, 2026, 8:51:51 AM (6 days ago)
Author:
Samuel Searles-Bryant

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #37368, comment 6

    initial v1  
    1 This change will cause `check_constraints` to fail on PostgreSQL (and maybe Oracle) if it is called outwith a transaction. That's reasonable: checking constraints in auto-commit mode doesn't make sense, but it is a change in behaviour.
     1The change in the PR will cause `check_constraints` to fail on PostgreSQL (and maybe Oracle) if it is called outwith a transaction. That's reasonable: checking constraints in auto-commit mode doesn't make sense, but it is a change in behaviour.
    22
    33We (Lily and I) think that `check_constraints` ought to raise a `TransactionManagementError` if called outwith a transaction in general. We would implement that by adding a check to the base class and calling `super()...` in the subclasses. We haven't done that in the PR because it probably needs a deprecation cycle, option to disable the behaviour temporarily, etc. Should we? Or can it be a separate change?
Back to Top