Opened 17 years ago

Closed 17 years ago

#6520 closed (wontfix)

NullBooleanSelect shouldn't use 'Unknown'

Reported by: Peter Baumgartner Owned by: nobody
Component: Forms Version: dev
Severity: Keywords: nullbooleanselect nullbooleanfield unknown
Cc: sgt.hulka@… 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

NullBooleanSelect should use u'---------' instead of ugettext('Unknown').

This matches the default empty_label for ModelChoiceField so newforms have a more uniform look. Unknown is not a synonym for Null. '---------' or are better text representations of Null.

Attachments (1)

nullbooleanselect_patch.diff​ (719 bytes ) - added by Peter Baumgartner 17 years ago.

Download all attachments as: .zip

Change History (4)

by Peter Baumgartner, 17 years ago

Attachment: nullbooleanselect_patch.diff​ added

comment:1 by Peter Baumgartner, 17 years ago

WikiFormatting got me. That should say '---------' or '' are better text representations of Null.

comment:2 by Chris Beaven, 17 years ago

Triage Stage: Unreviewed → Design decision needed

Potentially... the only problem is that '-------' might imply that you need to change it.

comment:3 by Malcolm Tredinnick, 17 years ago

Resolution: → wontfix
Status: new → closed

I think this is a bit of a judgement call, but what we've got at the moment feels a bit clearer. "Unknown" is precisely what NULL means at the database level, so there's no semantic mismatch there.

Because of the backwards incompatibility this would introduce and the fact that the current text makes it really clear there are three choices here, not just two plus a "you haven't set this yet" option, let's leave it as it is.

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