Code

#19365 closed Bug (wontfix)

Create a `NonNegativeIntegerField` alias for `PositiveIntegerField`

Reported by: Alex 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.

Attachments (0)

Change History (3)

comment:1 Changed 17 months ago by charettes

What about naming the alias UnsignedIntegerField.

comment:2 Changed 14 months ago by ramiro

  • 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 14 months ago by ramiro (next)

comment:3 Changed 14 months ago by jacob

  • Resolution set to wontfix
  • Status changed from new to 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.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.