Changes between Initial Version and Version 1 of Ticket #13776, comment 13


Ignore:
Timestamp:
Feb 28, 2014, 2:50:18 AM (11 years ago)
Author:
ANUBHAV JOSHI

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #13776, comment 13

    initial v1  
    1 Currently if blank=True and null is not True, ValueError is raised. The check being in related.py #399 for ForeignKey.
     1Currently if blank=True and null is not True, ValueError is raised. The check being in related.py line 399 for ForeignKey.
    22a.) I think we can display a correct message depicting the problem that in ForeignKey with null=True can only be left blank.
    33b.) 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
Back to Top