You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think that FooEvent shouldn't have slug field with unique constraint as it prevents multiple tracking events for same Foo record.
Next, it is working correctly for plain CharField with explicit unique=True (constraint is not present in the event model). The problem seems to be custom fields with implicit defaults which deviates from Django's defaults.
Thanks for any opinion to this topic.
The text was updated successfully, but these errors were encountered:
Will leave this open as a known bug. I imagine the solution may be straightforward if someone wants to try to address it. I wont be able to get to this anytime soon
Example:
Which leads to following migration:
I think that
FooEvent
shouldn't haveslug
field with unique constraint as it prevents multiple tracking events for sameFoo
record.Next, it is working correctly for plain
CharField
with explicitunique=True
(constraint is not present in the event model). The problem seems to be custom fields with implicit defaults which deviates from Django's defaults.Thanks for any opinion to this topic.
The text was updated successfully, but these errors were encountered: