Changes between Initial Version and Version 1 of Ticket #34943, comment 3
- Timestamp:
- Nov 2, 2023, 7:38:45 PM (12 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #34943, comment 3
initial v1 29 29 unique_constraint='unique_profile_stream_topic', 30 30 ) 31 32 --- 33 34 My recommendation would be to introduce a `unique_constraint: str | tuple[str | Expression]` kwarg and deprecate `unique_fields`. When provided a `str` it would be a reference to a `UniqueConstraint` by `.name` and when it's a `tuple` it would be expected to be a index expression where `str` are resolved to field names. I guess the `str` -> `UniqueConstraint.name` part could be a distinct feature request.