17.10.2012 14:28, Michał Nowotka kirjoitti:
Even if I don't mention inspectdb the problem still persists.
The basic question is how to map oracle NUMBER type from some model type.
If I understand this correctly, currently this is not supported.
In principle models.FloatField should handle it and
Anyway, Jani, thank you for pointing me to the software, I will give it a try.
--
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
Even if I don't mention inspectdb the problem still persists.
The basic question is how to map oracle NUMBER type from some model type.
If I understand this correctly, currently this is not supported.
In principle models.FloatField should handle it and give and option to
decide if the filed should
17.10.2012 12:15, Michał Nowotka kirjoitti:
Hello,
I have some legacy oracle database against which I run inspectdb command.
One column in the DB has type NUMBER (without precision and scale) and
what I got from django is:
entity_id = models.DecimalField(unique=True, null=True, max_digits=0,
Hello,
I have some legacy oracle database against which I run inspectdb command.
One column in the DB has type NUMBER (without precision and scale) and
what I got from django is:
entity_id = models.DecimalField(unique=True, null=True, max_digits=0,
decimal_places=-127, blank=True)
If I now run
5 matches
Mail list logo