diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt
index 66bb836..daa555e 100644
a
|
b
|
storage engine, you have a couple of options.
|
228 | 228 | |
229 | 229 | .. _AlterModelOnSyncDB: http://code.djangoproject.com/wiki/AlterModelOnSyncDB |
230 | 230 | |
| 231 | BooleanFields |
| 232 | ------------- |
| 233 | |
| 234 | In Django when you use a :class:`~django.db.models.fields.BooleanField` with |
| 235 | MySQL Django will actually create an integer column. This means that when |
| 236 | retrieving a value you will get `1` and `0` instead of `True` and `False`. This |
| 237 | is usually not an issue in your code, because in Python they are completely |
| 238 | equal(bool is actually a subclass of int). However it does mean that if you |
| 239 | want to write portable tests you should test for equality, not output:: |
| 240 | # bad |
| 241 | >>> my_obj.bool |
| 242 | True |
| 243 | |
| 244 | # good |
| 245 | >>> my_obj.bool == True |
| 246 | True |
231 | 247 | |
232 | 248 | .. _oracle-notes: |
233 | 249 | |