test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Reverted [3184]. There's no such thing as models.PasswordField. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@3189 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2006-06-21 14:42:52 +00:00
parent 68cfd446a3
commit a159f660fe
1 changed files with 0 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/model-api.txt
View File

@ -322,19 +322,6 @@ 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``
~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~