Add to the previous modification of Oracle backend, a flag in the options that makes it treat numbers as floats/ints unless there's a reason to think they are decimal. Makes things a little faster where relevant (and a little more cross-database-compatible, where expressions are concerned).
Removed the slow _rowfactory function and replaced it with a cx_Oracl…
…e 5 outputtypehandler function that operates only on each column, instead of each returned value.
Fix to _outputtypehandler fix: Use module-level function instead of m…
(because using a method ends up leaking cursors)
while at it: rename to_unicode ==> _to_unicode to conform with file's standard
Duplicate percent signs in names in quote_name() so the names can be …
…used in statements
Documentation: update cx_Oracle requirement to 5.0.1
Added the "float_is_enough" option to accelerate things
Fix phrasing of cx_Oracle version requirement change in docs.
Documentation for 'float_is_enough' flag in Oracle OPTIONS
This is a misguided idea based on wrong assumptions, as was pointed out to me by Anssi in https://groups.google.com/d/msg/django-developers/f0nF4vhavOQ/I2n_7TmSd4MJ.