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 13161,Avoid global registration of psycopg2 adapters/extensions,spoksss,nobody,"Hi, I have some problem while I use Django connection based on psycopg2 in the same time while using some other database application. Because Django changes default psycopg2 settings (psycopg2.extensions.register_type(psycopg2.extensions.UNICODE)), I get ""psycopg2.InterfaceError: can't decode into unicode string from SQLASCII"", when I try use my external database application which works with SQLASCII after import django settings. I think it isn't good way when Django changes default, global settings of psycopg2, because other application can have problems. I have read documentation of psycopg2, and it is possible to set that psycopg2.extensions.UNICODE just for custom connection or cursor, so I think it is good idea to use that feature in Django. http://initd.org/psycopg/docs/extensions.html#psycopg2.extensions.register_type I have tested my changes with psycopg 2.0.8 and Django-1.2-beta-1 and everything work correctly.",Cleanup/optimization,closed,"Database layer (models, ORM)",dev,Normal,wontfix,"psycopg2, unicode",Carl Meyer Florian Apolloner,Accepted,1,0,1,0,0,0