I think you mixed many things here.

First of all db_table = 'schema_name\".\"table_name' is a well known
hack to make django support Oracle multiple schemas.
So this is not a bug, but it would be nice if we have better solution.

As the consequence of this hack django treats the hole db_table string
as table name which is not true in this case.

But what is really buggy here is if i explicitly specify that this
table is not managed django should respect db_table and not perform
any truncation. That's all.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to