Hi Jon,
On 07/02/2014 09:06 PM, Jon Dufresne wrote:
> I'm reporting this to the developers list as I feel this shows a
> shortfall in (to me) expected behavior. I'm not sure this is exactly a
> bug or simply a use case the unique validation wasn't designed for.
>
> Basically, sometimes I want to
On Thu, Jul 3, 2014 at 10:48 AM, Florian Apolloner
wrote:
>
>
> On Thursday, July 3, 2014 3:03:25 PM UTC+2, Jon Dufresne wrote:
>>
>> > Also, even if we find a place to show
>> > the errors, the user is (usually) in no position to correct them (after
>> > all,
>> > there is no field he could chang
The problem is when a subset of the fields in a unique_together constraint
are in the form.
On Thu, Jul 3, 2014 at 11:48 AM, Florian Apolloner
wrote:
>
>
> On Thursday, July 3, 2014 3:03:25 PM UTC+2, Jon Dufresne wrote:
>>
>> > Also, even if we find a place to show
>> > the errors, the user is
On Thursday, July 3, 2014 3:03:25 PM UTC+2, Jon Dufresne wrote:
>
> > Also, even if we find a place to show
> > the errors, the user is (usually) in no position to correct them (after
> all,
> > there is no field he could change to fix it).
>
> I don't follow. In my specific example the user
I, too, struggle with this frequently.
On Wednesday, July 2, 2014 9:07:04 PM UTC-6, Jon Dufresne wrote:
>
> I'm reporting this to the developers list as I feel this shows a
> shortfall in (to me) expected behavior. I'm not sure this is exactly a
> bug or simply a use case the unique validation w
On Thu, Jul 3, 2014 at 7:02 AM, Tim Graham wrote:
> Another suggestion: could you include the field on the form but use a
> HiddenInput widget?
I could, but originally I wanted to avoid this. The container_id
should not be editable by the user. Including this in the form seems
to make a statement
Another suggestion: could you include the field on the form but use a
HiddenInput widget?
On Thursday, July 3, 2014 9:03:25 AM UTC-4, Jon Dufresne wrote:
>
> On Thu, Jul 3, 2014 at 1:12 AM, Florian Apolloner > wrote:
> > To me this is no shortfall but expected and good behaviour, including
> o
On Thu, Jul 3, 2014 at 1:12 AM, Florian Apolloner wrote:
> To me this is no shortfall but expected and good behaviour, including other
> fields in the validation (i.e. fields not on the form) would be very
> confusing. Where would errors show up?
Right now unique violations show up as non-field e
Hi Jon,
To me this is no shortfall but expected and good behaviour, including other
fields in the validation (i.e. fields not on the form) would be very
confusing. Where would errors show up? Also, even if we find a place to
show the errors, the user is (usually) in no position to correct them
I'm reporting this to the developers list as I feel this shows a
shortfall in (to me) expected behavior. I'm not sure this is exactly a
bug or simply a use case the unique validation wasn't designed for.
Basically, sometimes I want to create model formsets that use a
limited number of model fields
10 matches
Mail list logo
