Was it intensional that .upper is used in base.py in various places?

The reason why I ask is, that in a dialect 3 Firebird database, object names (tables, fields, ...) can be case-sensitive. Currently when I'm trying to access a case-sensitive table/object, this fails, because the accessed table gets uppered behind the scene in base.py.

Yes, there are no reason to use .upper() method. Apparently, it's unnecesary. But... I've a database (firebird 1.5). All database objects are uppercase. Then, if quote_name() in base.py, return no uppercase objects names, the query fail, because, (for instance) "DJANGO_SESSION" != "django_session".

What's wrong here? What approach do you think could be the correct?

Hi!

What's the value of db_table in your class? Is it lower-case? If so, try to make it the same casing as it is in the database and see, if it works with using upper(), lower() in base.py.