Re: modelformset_factory and unique_together don't always validate unique fields

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

Re: modelformset_factory and unique_together don't always validate unique fields

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

Re: modelformset_factory and unique_together don't always validate unique fields

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

position of deferred rendering code

I have a small app for logging errors to the database: I just moved the logging mechanism from middleware to a logging handler because the deferred rendering of TemplateResponse objects is 'outside' the exception handling middleware. I'm just curiou

Re: modelformset_factory and unique_together don't always validate unique fields

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

Re: modelformset_factory and unique_together don't always validate unique fields

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

Re: collectstatic - override default ignore list

On Thu, Jul 3, 2014 at 3:12 AM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > My concern -- and the reason why I started talking about an API -- is, > if every app clutters the AppConfig namespace with arbitrary names, > improvements to AppConfig may create name clashes. > Hence

Re: modelformset_factory and unique_together don't always validate unique fields

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

Re: modelformset_factory and unique_together don't always validate unique fields

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

Re: FormWizard needs confirmation step logic. ticket #21644

> > If we did split it out, would you be interested in being a maintainer? > > I was against this at first but the more I've thought about it, I would be interested. Has anyone else expressed any interest or will I be the only maintainer? I have another project coming up that will most likely

Re: modelformset_factory and unique_together don't always validate unique fields

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

Re: modelformset_factory and unique_together don't always validate unique fields

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