On Thu, Dec 13, 2012 at 1:19 PM, Michał Nowotka <mmm...@gmail.com> wrote:
> OK, then why django makes a difference between BigIntegerField (maps to > NUMBER(19)) and IntegerField (maps to NUMBER (11)). BigInteger was added after the others, probably by someone who did not notice/understand why the other two were defined as they were. When testing out that patch for inclusion I focused on "does the new field accept the range of numbers it should" and likely didn't check to make sure the new type defined for each backend was consistent with how other types in that backend had been specified... Karen -- http://tracey.org/kmt/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
