#19884: Inspectdb on Oracle doesn't produce correct field types
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.4
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by Shai Berger <shai@…>):
In [changeset:"e9d12bae1e59e51738c11c492c620f56f96106bf"]:
{{{
#!CommitTicketReference repository=""
revision="e9d12bae1e59e51738c11c492c620f56f96106bf"
Made Oracle introspect FloatFields correctly
Broke InspectDBTestCase.test_field_types in two:
- a test_number_field_types, which now passes on Oracle too
- a test_field_types, for all non-numeric fields, which is still expected
to fail
Also made some pep8 fixes in the tests file. Refs #19884
Thanks Tim Graham for review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/19884#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.bbf4d956bafc2aa2484b5226ca7ee5cd%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.