Re: [Django] #13776: is_valid() with null field value on ModelForms from models with non-nullable ForeignKeys causes ValueError

[Django]

#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
-+-
 Reporter:  peterbe  |Owner:
 |  anubhav9042
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  ModelForm| Triage Stage:  Accepted
  ForeignKey |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"158b0a28374054b1c3f94a9602b69f93fc980448" 158b0a28]:
 {{{
 #!CommitTicketReference repository=""
 revision="158b0a28374054b1c3f94a9602b69f93fc980448"
 [1.8.x] Fixed #25431 -- Readded inline foreign keys to modelformset
 instances

 Too much field exclusions in form's construct_instance() in _post_clean()
 could lead to some unexpected missing ForeignKey values.
 Fixes a regression from 45e049937. Refs #13776.

 Backport of 65a1055a3 from master.
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.3ff4596a51a9553d7197c9df63392d6e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #13776: is_valid() with null field value on ModelForms from models with non-nullable ForeignKeys causes ValueError

[Django]

#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
-+-
 Reporter:  peterbe  |Owner:
 |  anubhav9042
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  ModelForm| Triage Stage:  Accepted
  ForeignKey |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"65a1055a36318ff4e21ffeb7c3dd62fa81892269" 65a1055]:
 {{{
 #!CommitTicketReference repository=""
 revision="65a1055a36318ff4e21ffeb7c3dd62fa81892269"
 Fixed #25431 -- Readded inline foreign keys to modelformset instances

 Too much field exclusions in form's construct_instance() in _post_clean()
 could lead to some unexpected missing ForeignKey values.
 Fixes a regression from 45e049937. Refs #13776.
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.6888de24cc3f7d1b25c0be153a8567f7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #13776: is_valid() with null field value on ModelForms from models with non-nullable ForeignKeys causes ValueError

[Django]

#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
-+-
 Reporter:  peterbe  |Owner:
 Type:  Bug  |  anubhav9042
Component:  Forms|   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:  ModelForm|   Resolution:  fixed
  ForeignKey | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"45e049937d2564d11035827ca9a9221b86215e45"]:
 {{{
 #!CommitTicketReference repository=""
 revision="45e049937d2564d11035827ca9a9221b86215e45"
 Fixed #13776 -- Fixed ModelForm.is_valid() exception with non-nullable FK
 and blank=True.

 Thanks peterbe for the report.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.6d9dcbc39d99beaa4366c0c90986e192%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #13776: is_valid() with null field value on ModelForms from models with non-nullable ForeignKeys causes ValueError

[Django]

#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
-+-
 Reporter:  peterbe  |Owner:
 Type:  Bug  |  anubhav9042
Component:  Forms|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:  ModelForm|   Resolution:
  ForeignKey | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timo):

 As discussed on IRC, the patch isn't what we want. There shouldn't be a
 form error because the form is valid according to its specification.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.0038a93088848466054167c265c65134%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #13776: is_valid() with null field value on ModelForms from models with non-nullable ForeignKeys causes ValueError

[Django]

#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
-+-
 Reporter:  peterbe  |Owner:
 Type:  Bug  |  anubhav9042
Component:  Forms|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:  ModelForm|   Resolution:
  ForeignKey | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anubhav9042):

 * has_patch:  0 => 1
 * version:  1.2 => master


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.25865ae8c25a7c4399b9a1985efe900e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #13776: is_valid() with null field value on ModelForms from models with non-nullable ForeignKeys causes ValueError

[Django]

#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
-+-
 Reporter:  peterbe  |Owner:
 Type:  Bug  |  anubhav9042
Component:  Forms|   Status:  assigned
 Severity:  Normal   |  Version:  1.2
 Keywords:  ModelForm|   Resolution:
  ForeignKey | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timo):

 We should try to fix it so that an exception is not raised. As noted in
 the django-users thread, the use-case worked in Django 1.0, but broke in
 1.2.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.ba2ca20211f75655d84cd6b731e694c6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #13776: is_valid() with null field value on ModelForms from models with non-nullable ForeignKeys causes ValueError

[Django]

#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
-+-
 Reporter:  peterbe  |Owner:
 Type:  Bug  |  anubhav9042
Component:  Forms|   Status:  assigned
 Severity:  Normal   |  Version:  1.2
 Keywords:  ModelForm|   Resolution:
  ForeignKey | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anubhav9042):

 Replying to [comment:16 timo]:
 > I think `blank=True` with `null=False` is acceptable. For example, you
 might fill in the value of the `ForeignKey` in the object's `save()`
 method.

 What about `is_valid`?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.70cde28939283ba797aef8a780fc7cf5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #13776: is_valid() with null field value on ModelForms from models with non-nullable ForeignKeys causes ValueError

[Django]

#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
-+-
 Reporter:  peterbe  |Owner:
 Type:  Bug  |  anubhav9042
Component:  Forms|   Status:  assigned
 Severity:  Normal   |  Version:  1.2
 Keywords:  ModelForm|   Resolution:
  ForeignKey | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timo):

 I think `blank=True` with `null=False` is acceptable. For example, you
 might fill in the value of the `ForeignKey` in the object's `save()`
 method.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.218a8ebadfbd672589e79e291221675c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #13776: is_valid() with null field value on ModelForms from models with non-nullable ForeignKeys causes ValueError

[Django]

#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
-+-
 Reporter:  peterbe  |Owner:
 Type:  Bug  |  anubhav9042
Component:  Forms|   Status:  assigned
 Severity:  Normal   |  Version:  1.2
 Keywords:  ModelForm|   Resolution:
  ForeignKey | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anubhav9042):

 I hope to work on this ticket for GSoC 2014.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.c374ca7520ecb1ad24db51fcf4e44f2b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13776: is_valid() with null field value on ModelForms from models with non-nullable ForeignKeys causes ValueError

[Django]

#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
-+-
 Reporter:  peterbe  |Owner:
 Type:  Bug  |  anubhav9042
Component:  Forms|   Status:  assigned
 Severity:  Normal   |  Version:  1.2
 Keywords:  ModelForm|   Resolution:
  ForeignKey | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anubhav9042):

 Currently if blank=True and null is not True, ValueError is raised. The
 check being in related.py #399 for ForeignKey.
 a.) I think we can display a correct message depicting the problem that in
 ForeignKey with null=True can only be left blank.
 b.) We can stop the usage of blank=True with ForeignKey, because alone
 without null=True defined it has no significance and give suitable error
 message instead of raising an error. null=True alone works perfectly

 Any opinions?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.a713a2b451cb32c2ae83e56bb94ee830%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13776: is_valid() with null field value on ModelForms from models with non-nullable ForeignKeys causes ValueError

[Django]

#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
-+-
 Reporter:  peterbe  |Owner:
 Type:  Bug  |  anubhav9042
Component:  Forms|   Status:  assigned
 Severity:  Normal   |  Version:  1.2
 Keywords:  ModelForm|   Resolution:
  ForeignKey | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anubhav9042):

 * cc: anubhav9042@… (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.a3344bc6689b0eeb53fc755a4b041fdd%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13776: is_valid() with null field value on ModelForms from models with non-nullable ForeignKeys causes ValueError

[Django]

#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
-+-
 Reporter:  peterbe  |Owner:
 Type:  Bug  |  anubhav9042
Component:  Forms|   Status:  assigned
 Severity:  Normal   |  Version:  1.2
 Keywords:  ModelForm|   Resolution:
  ForeignKey | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anubhav9042):

 * owner:  elektrrrus => anubhav9042


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.cd7321832113c55e13109a37b0c5a952%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13776: is_valid() with null field value on ModelForms from models with non-nullable ForeignKeys causes ValueError

[Django]

#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
-+-
 Reporter:  peterbe  |Owner:
 Type:  Bug  |  elektrrrus
Component:  Forms|   Status:  assigned
 Severity:  Normal   |  Version:  1.2
 Keywords:  ModelForm|   Resolution:
  ForeignKey | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mjumbewu):

 * cc: mjumbewu (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.cc175c5ef3bdd2cca9b16761ff8e67d5%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13776: is_valid() with null field value on ModelForms from models with non-nullable ForeignKeys causes ValueError

[Django]

#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
-+-
 Reporter:  peterbe  |Owner:
 Type:  Bug  |  elektrrrus
Component:  Forms|   Status:  assigned
 Severity:  Normal   |  Version:  1.2
 Keywords:  ModelForm|   Resolution:
  ForeignKey | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by elektrrrus):

 * owner:  nobody => elektrrrus
 * status:  new => assigned


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.f9991cd547dd666c59316bfcf0ca33e8%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13776: is_valid() with null field value on ModelForms from models with non-nullable ForeignKeys causes ValueError

[Django]

#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
--+
 Reporter:  peterbe   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  Version:  1.2
 Severity:  Normal|   Resolution:
 Keywords:  ModelForm ForeignKey  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by jacob):

 * stage:  Design decision needed => Accepted


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13776: is_valid() with null field value on ModelForms from models with non-nullable ForeignKeys causes ValueError

[Django]

#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
-+-
 Reporter:  peterbe  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  ModelForm| Triage Stage:  Design
  ForeignKey |  decision needed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 #18441 was a duplicate

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13776: is_valid() with null field value on ModelForms from models with non-nullable ForeignKeys causes ValueError

[Django]

#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
-+--
  Reporter:  peterbe | Owner:  nobody   
   
Status:  new | Milestone:   
   
 Component:  Forms   |   Version:  1.2  
   
Resolution:  |  Keywords:  ModelForm 
ForeignKey
 Stage:  Design decision needed  | Has_patch:  0
   
Needs_docs:  0   |   Needs_tests:  0
   
Needs_better_patch:  0   |  
-+--
Changes (by romke):

 * cc: romke (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13776: is_valid() with null field value on ModelForms from models with non-nullable ForeignKeys causes ValueError

[Django]

#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
-+--
  Reporter:  peterbe | Owner:  nobody   
   
Status:  new | Milestone:   
   
 Component:  Forms   |   Version:  1.2  
   
Resolution:  |  Keywords:  ModelForm 
ForeignKey
 Stage:  Design decision needed  | Has_patch:  0
   
Needs_docs:  0   |   Needs_tests:  0
   
Needs_better_patch:  0   |  
-+--
Changes (by Joshua Ginsberg ):

  * summary:  is_valid() on ModelForms on models with ForeignKeys cause
  ValueError rather than False => is_valid() with
  null field value on ModelForms from models with
  non-nullable ForeignKeys causes ValueError
  * stage:  Accepted => Design decision needed

Comment:

 In #6886 with r8185 we introduced the requirement for the reverse
 descriptor that null and wrong-model assignments to !ForeignKey fields
 would be disallowed prior to save-time. In r12098 with the model-
 validation merge, we changed the operation of !ModelForms to construct
 instances at validation time, not at save-time. The combination of these
 two limits the developer's ability to preeempt the automated validation
 with !ForeignKeys. For another example, see
 [http://groups.google.com/group/django-
 users/browse_thread/thread/8ea803cb8a28e594 this other thread] - a user's
 model populates a non-nullable FK with an overridden save method which
 would satisfy the not-null requirement, but the !ModelForm created by the
 admin throws an error before save-time.

 This requires some core developer time to figure out how to proceed.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.