According to the docs, oracle uses 1 byte for the magnitude, and 1 or more bytes for significant digits.
HOWEVER, it assigns that space dynamically, so even if you say NUMBER(11), you will still only need 2 bytes to represent the number "5". All NUMBER(11) gives you is some range checking on input. So, from that, I read that there's no real benefit from using SmallIntegerField, since it'll still only take up as much space as you need. Any range checking can be done in the Model's save method, or a Form's clean methods, and be much more specific to the application's requirements than oracle's range checking can provide. On Thursday, December 13, 2012 9:28:22 AM UTC-8, Tom Evans wrote: > > Oracle may use the exact same datatype underneath for all NUMBER > (speculation). The value in brackets could simply be the default > number of digits presented. > > Cheers > > Tom > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/gUOxBXSB8B0J. 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.
