Opened 8 years ago

Closed 8 years ago

Last modified 5 years ago

#8802 closed (fixed)

Document database-dependent behavior of BooleanField.

Reported by: stengleind Owned by: Jacob
Component: Documentation Version: master
Severity: Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

As noted in http://code.djangoproject.com/ticket/7190, BooleanField can be either an int or a bool depending on the database used.

This bit of non-deterministic behavior should be documented very clearly.

-Dave

Attachments (1)

django-mysql-bool-note.diff (921 bytes) - added by Alex Gaynor 8 years ago.

Download all attachments as: .zip

Change History (7)

Changed 8 years ago by Alex Gaynor

Attachment: django-mysql-bool-note.diff added

comment:1 Changed 8 years ago by Alex Gaynor

Component: UncategorizedDocumentation
Has patch: set
Triage Stage: UnreviewedAccepted

comment:2 Changed 8 years ago by stengleind

Looks like the doc in the code should be updated. There is a fine difference between bool and int:

1 == True

True

1 is True

False

-Dave

comment:3 Changed 8 years ago by Alex Gaynor

milestone: 1.0

comment:4 Changed 8 years ago by Jacob

Owner: changed from nobody to Jacob
Status: newassigned

comment:5 Changed 8 years ago by Malcolm Tredinnick

Resolution: fixed
Status: assignedclosed

(In [8910]) Fixed #8802 -- Documented MySQL's usage of 1/0 instead of True/False for model
BooleanFields.

comment:6 Changed 5 years ago by Jacob

milestone: 1.0

Milestone 1.0 deleted

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