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
24920	Database type NUMERIC with no parameters is not supported	Shai Berger	Mariusz Felisiak	"Django's `DecimalField` requires both `max_digits` and `decimal_places`. Database backends allow them to be dropped, to specify an ""unlimited precision"" field.

This leads to bugs in `inspectdb`: On Oracle, a column defined as `NUMERIC` is inspected as having 0 digits and negative precision; on Postgresql, it is inspected as having 65535 (a C short -1?) digits and decimal places, when the [http://www.postgresql.org/docs/9.4/static/datatype-numeric.html documentation] says you can only explicitly define up to 1000 decimal places (and even the implicitly defined precision is only 16383).

Discussion in the context of Oracle (from 2012):
https://groups.google.com/d/topic/django-developers/qSAfzPyqKqw/discussion

(This could be solved more easily by adding a new field type than by modifying the behavior of the existing `DecimalField`; however, I'm having a hard time suggesting a name for such a field type, which may be an indication that it is a bad interface. Besides that decision, this probably applies as an easy picking)."	New feature	closed	Database layer (models, ORM)	dev	Normal	fixed	oracle		Ready for checkin	1	0	0	0	0	0