Opened 18 years ago

Closed 17 years ago

#3328 closed (wontfix)

null=True should imply blank=True

Reported by: Chris Beaven Owned by: nobody
Component: Database layer (models, ORM) Version: dev
Severity: Keywords:
Cc: Triage Stage: Design decision needed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

For models, I can't ever think of a case when you would want null=True and not want blank=True. If there is, it's definitely rare, so having to enter both for the normal case seems redundant.

Currently, for model fields, blank always defaults to False.

This proposal is that blank is set to whatever null is set to unless explicitly given.

Attachments (1)

imply_blank.patch​ (1.6 KB ) - added by Chris Beaven 18 years ago.
patch, including doc

Download all attachments as: .zip

Change History (3)

by Chris Beaven, 18 years ago

Attachment: imply_blank.patch​ added

patch, including doc

comment:1 by Chris Beaven, 18 years ago

Triage Stage: Unreviewed → Design decision needed

comment:2 by James Bennett, 17 years ago

Resolution: → wontfix
Status: new → closed

These options need to remain separate; I can think of use cases where you'd want to require the user to input something, and then decide whether to store it in the DB during processing.

Note: See TracTickets for help on using tickets.
Back to Top