#4551: Documentation is wrong about PhoneNumberField subclass
-----------------------------------+----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: jacob
Status: closed | Component: Documentation
Version: SVN | Resolution: wontfix
Keywords: | Stage: Ready for checkin
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-----------------------------------+----------------------------------------
Changes (by russellm):
* status: new => closed
* resolution: => wontfix
Comment:
This is a bit of a wierd one. PhoneNumberField extends IntegerField, but
only to get the 'empty_string_allowed' setting, and avoid the to_python
coercion on a CharField. At the database level, PhoneNumberField is a
VARCHAR(20). So, strictly, it is a character field, although not a
CharField. It definitely stores char data though, so I think in the name
of end-user clarity, the existing documentation is probably the best
option.
--
Ticket URL: <http://code.djangoproject.com/ticket/4551#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
