On Tue, Oct 21, 2008 at 2:35 PM, bobhaugen <[EMAIL PROTECTED]> wrote:
>
> On Oct 21, 12:34 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> > Well then the next step I would try is testing out the current patch for
> > general model validation, which is ticket #6845:
> >
> >
On Oct 21, 12:34 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> Well then the next step I would try is testing out the current patch for
> general model validation, which is ticket #6845:
>
> http://code.djangoproject.com/ticket/6845
>
> Status on this was most recently reported here, I think:
>
On Tue, Oct 21, 2008 at 12:36 PM, bobhaugen <[EMAIL PROTECTED]> wrote:
>
> On Oct 21, 10:59 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> > Have you tried whatever scenario you are particularly interested in on
> 1.0
> > or current code?
> >
> > Though general model validation did not make it
On Oct 21, 10:59 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> Have you tried whatever scenario you are particularly interested in on 1.0
> or current code?
>
> Though general model validation did not make it into 1.0, checking of unique
> and unique_together was added in changeset [8805]. It
On Tue, Oct 21, 2008 at 11:39 AM, bobhaugen <[EMAIL PROTECTED]> wrote:
>
> I mean the normal displayable and user-correctable form validation
> errors, not the fatal database IntegrityError.
>
> I found
>
I mean the normal displayable and user-correctable form validation
errors, not the fatal database IntegrityError.
I found
http://groups.google.com/group/django-users/browse_thread/thread/f0e245366b02411b/df6d03f32eb37f93
and
http://www.djangosnippets.org/snippets/338/
both more than a year old.
6 matches
Mail list logo