Hi Simon,
Cheers for the explanation.
I'm ok with the error message being the "constraint is violated" generic
message as I agree with what you're saying.
Would it be possible to group the message by field in the same way as
standard unique?
ie, would this be an idea?:
django.core.exceptions.V
Hello David,
This is expected because Django doesn't have a way to express the
constraint in words to present to the user when a condition, which could be
complex, is provided.
When no conditions are defined the metadata is easy to interpret to form a
sentence out of ("Foo with this field0, fi
nice one there
On Sun, Sep 11, 2022 at 3:36 PM David Sanders
wrote:
> Hi folks (and in particular Simon Charette),
>
> I had a bit of a gotcha moment when a custom unique constraint validation
> message disappeared when I added a condition to it. I won't raise a ticket
> for this because it look
Hi folks (and in particular Simon Charette),
I had a bit of a gotcha moment when a custom unique constraint validation
message disappeared when I added a condition to it. I won't raise a ticket
for this because it looks intentional from the constraint validation PR,
but I wanted to seek clarificat
