Changes between Initial Version and Version 1 of Ticket #36627, comment 1


Ignore:
Timestamp:
Sep 26, 2025, 8:58:03 PM (3 weeks ago)
Author:
Simon Charette

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #36627, comment 1

    initial v1  
    33The hard part here will likely not be to write the `WithoutOverlaps` expression part but to adjust `UniqueConstraint.validate` to honor it without coupling `contrib.postgres` and core.
    44
    5 I'll note that `WITHOUT OVERLAPS` is really just SQL sugar over exclusion constraints which we already support via `ExclusionConstraint` so I'm not entirely convinced it's worth adding given the `UniqueConstraint.validate` complexity it would incur.
     5I'll note that `WITHOUT OVERLAPS` is really just SQL sugar over exclusion constraints which we already support via `ExclusionConstraint` so I'm not entirely convinced it's worth adding given the `UniqueConstraint.validate` complexity it would incur. If it was supported by more than one supported engine then it could be worthy but AFAIK it's not the case.
Back to Top