Re: IntegerField and SmallIntegerFields maps to the same db type on Oracle.

2012-12-13 Thread Karen Tracey
On Thu, Dec 13, 2012 at 1:19 PM, Michał Nowotka 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

Re: IntegerField and SmallIntegerFields maps to the same db type on Oracle.

2012-12-13 Thread Chris Cogdon
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 in

Re: IntegerField and SmallIntegerFields maps to the same db type on Oracle.

2012-12-13 Thread Michał Nowotka
OK, then why django makes a difference between BigIntegerField (maps to NUMBER(19)) and IntegerField (maps to NUMBER (11)). Thinking this way BigIntegerField, IntegerField and SmallIntegerField should all map to NUMBER(39). -- You received this message because you are subscribed to the Google Gro

Re: IntegerField and SmallIntegerFields maps to the same db type on Oracle.

2012-12-13 Thread Tom Evans
On Thu, Dec 13, 2012 at 4:50 PM, Michał Nowotka wrote: > I agree, but if you map SmallIntegerField to say NUMBER(9) you will save > some space, correct? > Oracle may use the exact same datatype underneath for all NUMBER (speculation). The value in brackets could simply be the default number of di

Re: IntegerField and SmallIntegerFields maps to the same db type on Oracle.

2012-12-13 Thread Michał Nowotka
I agree, but if you map SmallIntegerField to say NUMBER(9) you will save some space, correct? -- 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, sen

Re: IntegerField and SmallIntegerFields maps to the same db type on Oracle.

2012-12-13 Thread Ian
On Thursday, December 13, 2012 4:29:30 AM UTC-7, Michał Nowotka wrote: > > Does anyone knows the reason why IntegerField and SmallIntegerFields both > map to NUMBER(11,0) in Orcale? > I would expect SmallIntegerFiled map to something smaller ;) > Beats me. Although note that Oracle itself equate

IntegerField and SmallIntegerFields maps to the same db type on Oracle.

2012-12-13 Thread Michał Nowotka
Does anyone knows the reason why IntegerField and SmallIntegerFields both map to NUMBER(11,0) in Orcale? I would expect SmallIntegerFiled map to something smaller ;) -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the