#2101: maxlength should be max_length
------------------------------+---------------------------------------------
Reporter: nirvdrum | Owner: adrian
Type: defect | Status: new
Priority: normal | Milestone:
Component: Database wrapper | Version:
Severity: normal | Keywords:
------------------------------+---------------------------------------------
I have a feeling this isn't going to go over too well, but the "maxlength"
parameter for the various field types should be "max_length." This really
isn't an issue about cosmetics, but rather one about consistency.
FloatField has "max_digits" and ForeignKey has "max_num_in_admin", while
CharField, CommaSeparatedIntegerField, and SlugField have "maxlength."
Many times I find myself going to type the parameter one way only to find
it should be the other way. It's one of those little gotchas in the
framework.
My personal recommendation would be to add the "max_length" parameter
without removing "maxlength." This way, backwards-compatibility can be
maintained while promoting consistency moving forward. The best of both
worlds.
--
Ticket URL: <http://code.djangoproject.com/ticket/2101>
Django <http://code.djangoproject.org/>
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
-~----------~----~----~----~------~----~------~--~---
