Opened 17 years ago

Closed 17 years ago

Last modified 14 years ago

#8802 closed (fixed)

Document database-dependent behavior of BooleanField.

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

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 17 years ago.

Download all attachments as: .zip

Change History (7)

by Alex Gaynor, 17 years ago

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

comment:1 by Alex Gaynor, 17 years ago

Component: Uncategorized → Documentation
Has patch: set
Triage Stage: Unreviewed → Accepted

comment:2 by stengleind, 17 years ago

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 by Alex Gaynor, 17 years ago

milestone: → 1.0

comment:4 by Jacob, 17 years ago

Owner: changed from nobody to Jacob
Status: new → assigned

comment:5 by Malcolm Tredinnick, 17 years ago

Resolution: → fixed
Status: assigned → closed

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

comment:6 by Jacob, 14 years ago

milestone: 1.0

Milestone 1.0 deleted

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