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.'),)
orokusaki
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 %-)
>
> The only idea I have for a solution is:
>
> class Meta:
> unique_together = (('account', 'name', 'You already have a
> Widget with this Name.'),)
[snip]
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.
On Apr 12, 5:38 am, Karen Tracey <kmtra...@gmail.com> wrote:
> On Sun, Apr 11, 2010 at 11:10 PM, Russell Keith-Magee <
>
>
>
> freakboy3...@gmail.com> wrote:
> > On Mon, Apr 12, 2010 at 10:15 AM, orokusaki <flashdesign...@gmail.com>
orokusaki <flashde...@gmail.com> wrote:
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-d...@googlegroups.com.
To unsubscribe from this group, send email to
django-develop...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.