"""
Devs: ALWAYS call model.full_clean() OR form.is_valid() to protect
Database from radical or duplicate DB entries!
* Calling model.full_clean() OR form.is_valid() calls 3 underlying
methods (clean, clean_fields, validate_unique)
"""
I haven't had to do much with form validation beyond w
On Tue, Jul 12, 2011 at 2:25 PM, Venkatraman S wrote:
>
>
> On Tue, Jul 12, 2011 at 9:12 PM, Andre Terra wrote:
>
>> May I ask if you are managing to do this (and, if so, how) without
>>> writing duplicate logic?
>>>
>>
>> This, to me, is a key area for improvement. Aside from the development
>>
On Tue, Jul 12, 2011 at 9:12 PM, Andre Terra wrote:
> May I ask if you are managing to do this (and, if so, how) without
>> writing duplicate logic?
>>
>
> This, to me, is a key area for improvement. Aside from the development
> challenge the idea imposes, an extra issue with writing DRY validati
Some interesting thoughts here. I once attempted to make a merge between
Django validation and jQuery validation (spent several weeks on it), but my
approach wasn't dynamic enough, and ended up not being used again.
Personally, I'd like to see some sort of standardized JS library which
works seaml
>
> May I ask if you are managing to do this (and, if so, how) without
> writing duplicate logic?
>
This, to me, is a key area for improvement. Aside from the development
challenge the idea imposes, an extra issue with writing DRY validation for
django and javascript is that the project doesn't of
On Jul 12, 10:15 am, Venkatraman S wrote:
> On Tue, Jul 12, 2011 at 1:23 PM, Cal Leeming [Simplicity Media Ltd] <
>
>
> cal.leem...@simplicitymedialtd.co.uk> wrote:
> > On 12 Jul 2011 08:13, "bruno desthuilliers"
> > wrote:
>
> > > On Jul 12, 3:37 am, Venkatraman S wrote:
>
> > > > On the valid
On Tue, Jul 12, 2011 at 1:23 PM, Cal Leeming [Simplicity Media Ltd] <
cal.leem...@simplicitymedialtd.co.uk> wrote:
> On 12 Jul 2011 08:13, "bruno desthuilliers"
> wrote:
> >
> > On Jul 12, 3:37 am, Venkatraman S wrote:
> > >
> > > On the validation, yes, it is a little pesky. But, offlate, i am
On 12 Jul 2011 08:13, "bruno desthuilliers"
wrote:
>
> On Jul 12, 3:37 am, Venkatraman S wrote:
> >
> > On the validation, yes, it is a little pesky. But, offlate, i am trying
to
> > *understand* it better and trying to move the logic
> > to the client. For eg. jquery-validate does bulk of the st
On Jul 12, 3:37 am, Venkatraman S wrote:
>
> On the validation, yes, it is a little pesky. But, offlate, i am trying to
> *understand* it better and trying to move the logic
> to the client. For eg. jquery-validate does bulk of the stuff on client side
> - atleast for required fields. So, moving
>
On Tue, Jul 12, 2011 at 4:26 AM, Cal Leeming [Simplicity Media Ltd] <
cal.leem...@simplicitymedialtd.co.uk> wrote:
> Does anyone else find working with form validation in Django to be a bit
> awkward and/or tedious?
>
> I can't say exactly why I don't like it, because I don't really know
> myself,
Does anyone else find working with form validation in Django to be a bit
awkward and/or tedious?
I can't say exactly why I don't like it, because I don't really know
myself, I just always disliked working with it.
Am I being a fussy little fuzz ball, or does anyone else have this same
view t
11 matches
Mail list logo
