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
304	Changes to auth.LogEntry in changeset [469] breaks Oracle backend.	Jason Huggins	Adrian Holovaty	"Changeset [469] added an additional ""TextField"" objects to the LogEntry model.

In the Oracle backend (#87), I mapped TextField types in Django to the ""Long"" datatype in the db, because the Model documentaton suggests TextFields should be used to store (potentially large) html content. If I used any other string datatype (like varchar2), the max length of the field would be 4000 characters/bytes. That isn't good. Yet, again, Oracle stinks compared to PostgreSQL, because Oracle only allows '''one''' ""Long"" field type per table.

If LogEntry's ""object_id"" needs to only hold small strings, and it is going to be less than 4000 characters, I'd suggest you change it to CharField.

After changeset #469, I get this error in django-admin.py init:
""""""
Error: The database couldn't be initialized. Here's the full exception:
ORA-01754: a table may contain only one column of type LONG
""""""

I've confirmed that changing LogEntry's object_id field to ""CharField"" fixes the problem for Oracle."	defect	closed	Database layer (models, ORM)		major	duplicate	oracle TextField CharField Long		Unreviewed	0	0	0	0	0	0