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
19198	Oracle specific failures	Anssi Kääriäinen	nobody	"Two Oracle specific failures have been introduced lately:
  - Inability to deal with ""%"" in table or other identifier names (present in 1.5a1)
  - Oracle not working correctly for select_related cases where the related model is null but contains character fields (master only)

The first of the failures happens because Oracle backend does querystr % args formatting and if a table name contains '%' then the formatting will fail.

The second one happens because we check for if all fetched columns are None then set related object to None in models/query.py when creating the related objects. Due to a recent change we correctly convert the row values in compiler.py for related select fields, too. This means that None values will be converted to """" and the check in models/query.py fails.

Draft patches available from: https://github.com/akaariai/django/compare/fix_oracle2"	Bug	closed	Database layer (models, ORM)	1.5-alpha-1	Normal	fixed	oracle		Ready for checkin	1	0	0	0	0	0