p31829507
/
django
mirror of https://github.com/django/django.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fixed #2071 -- documented the PasswordField (including cavaets). Thanks to 

asmodai for the initial patch.


git-svn-id: http://code.djangoproject.com/svn/django/trunk@3184 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick 2006-06-21 04:49:12 +00:00
parent b70a687777
commit c4fa8a158a
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/model-api.txt
View File

@ -322,6 +322,19 @@ instead of a ``BooleanField`` with ``null=True``.
The admin represents this as a ``<select>`` box with "Unknown", "Yes" and "No" choices. The admin represents this as a ``<select>`` box with "Unknown", "Yes" and "No" choices.
``PasswordField``
~~~~~~~~~~~~~~~~~
A ``PasswordField`` is like a ``TextField`` but the characters that are
entered are masked, typically by asterisks (*), when entered into a form. Note
that though the data is masked on entry, it is sent as clear text to the
server and stored as plain text in the database. Additional measures (such as
using HTTPS) are needed to ensure the security of data sent from a form. This
field is probably more useful when used in a `custom manipulator`_ than
directly in a model.
.. _custom manipulator: http://www.djangoproject.com/documentation/forms/#custom-forms-and-manipulators
``PhoneNumberField`` ``PhoneNumberField``
~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~