Opened 12 years ago

Closed 12 years ago

#19365 closed Bug (wontfix)

Create a `NonNegativeIntegerField` alias for `PositiveIntegerField`

Reported by: Alex Gaynor Owned by: nobody
Component: Database layer (models, ORM) Version: 1.4
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no

Description

The current name is totally bogus, we should at least have an alias that's correct.

Change History (3)

comment:1 by Simon Charette, 12 years ago

What about naming the alias ​UnsignedIntegerField.

comment:2 by Ramiro Morales, 12 years ago

Has patch: set

I've started a branch using the name propossed by charettes:

​https://github.com/ramiro/django/compare/t19365-positiveintegerfield-alias

I wonder how changes like this interact with South migrations and if there is something we need to to differently. Opinions and hints welcome.

Version 0, edited 12 years ago by Ramiro Morales (next)

comment:3 by Jacob, 12 years ago

Resolution: → wontfix
Status: new → closed

I'm -1 on this change: "there should be one -- and preferably only one -- way to do it." I don't see the need to have multiple names for the same field. Yes, the name isn't perfect, but it's fine.

Note: See TracTickets for help on using tickets.
Back to Top