On Mon, Apr 12, 2010 at 10:15 AM, orokusaki <[email protected]> wrote: > The idea is basically to allow for the customization of the error > message that's raised during ``validate_unique()``. > > Example Error: > Widget with this Account and Name already exists. > > More Useful Error: > You already have a Widget with this Name. > > (The only key difference is that if a field is hidden like "Account", > I don't necessarily want the client to see it.) > > The only idea I have for a solution is: > > class Meta: > unique_together = (('account', 'name', 'You already have a > Widget with this Name.'),)
This really isn't the best time to be proposing new features. We're a handful of tickets away from the 1.2 final release, so the focus of the core team is on finishing what we've started, rather than starting something new. That said - my initial reaction is that while I agree with the use case, I'm not a huge fan of the syntax - There is not syntactic separation between column names and error messages; while that isn't necessarily syntactically ambiguous, it's certainly conceptually ambiguous. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
