Skip to content

Commit

Permalink
Reverted [3184]. There's no such thing as models.PasswordField.
Browse files Browse the repository at this point in the history
git-svn-id: http://code.djangoproject.com/svn/django/trunk@3189 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information
adrianholovaty committed Jun 21, 2006
1 parent 68cfd44 commit a159f66
Showing 1 changed file with 0 additions and 13 deletions.
13 changes: 0 additions & 13 deletions docs/model-api.txt
Expand Up @@ -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.

``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``
~~~~~~~~~~~~~~~~~~~~

Expand Down

0 comments on commit a159f66

Please sign in to comment.