On Wed, 2012-10-17 at 12:16 -0600, Ian Kelly wrote: > > Do you know what type in model will map to NUMBER in oracle? > > There is none. The proper type would be a floating-point > DecimalField, but Django doesn't allow that as the decimal_places > attribute is required. I'm not really sure why that is; maybe the > requirement could be relaxed? > > If you don't need a lot of precision, then you could probably get away > with using a FloatField. Otherwise you might want consider creating a > custom field that looks like a FloatField but uses decimals instead of > floats. >
Not if you have a "legacy" database which uses NUMBER, I'm guessing... I'd have thought the inability to work with any particular common field type should be a bug, as it could effectively prevent working with non-managed models altogether. Cheers, Nick -- Nick Phillips / +64 3 479 4195 / nick.phill...@otago.ac.nz # these statements are my own, not those of the University of Otago -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
