id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
11049	Oracle fails to return IntegerField in test_get_table_description_types	Matt Boersma	Matt Boersma	"The Oracle backend raises an AssertionError when executing test_get_table_description_types in the test suite:

{{{
C:\projects\django-1.0.x\tests>runtests.py --settings=testsettings.oracle introspection
...

======================================================================
FAIL: test_get_table_description_types (regressiontests.introspection.tests.IntrospectionTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File ""C:\projects\django-1.0.x\tests\regressiontests\introspection\tests.py"", line 28, in _inner
    return func(*args, **kwargs)
  File ""C:\projects\django-1.0.x\tests\regressiontests\introspection\tests.py"", line 80, in test_get_table_description_types
    ['IntegerField', 'CharField', 'CharField', 'CharField'])
AssertionError: ['DecimalField', 'CharField', 'CharField', 'CharField'] != ['IntegerField', 'CharField', 'CharField', 'CharField']
}}}

Oracle doesn't have a distinct data type for integers as opposed to floating point numbers; they all come across as cx_Oracle.NUMERIC.  Either we should use a different approach during introspection, or this test case should be changed so this isn't considered an error when run against Oracle.

This happens in both the 1.0.x maintenance branch and the pre-1.1 trunk as of revision [10723]. It hasn't caused real-world problems as far as I know, but I've entered it here as a bug so we don't lose track of it."		closed	Database layer (models, ORM)	dev		fixed	Oracle oracle	Erin Kelly	Accepted	1	0	1	0	0	0