For example in PostgreSQL, at least from the 8.3 version, you can't have, in the same server, databases with differents encoding. But can be defined a client_encoding for any database. With this you can have a database with encoding='latin1' and client_encoding='utf8'. In postgresql the client_encoding is a connection property to solve this problems and avoid complications with weird characters.
However for any encoding just some client_encodings are valid. To latin1 is valid a client_encoding=utf8 but isn't valid a client_encoding=EUC_TW (traditional Chinese, Taiwanese). For that is important read the PostgreSQL documentation. Well, I don't know if you're using PostgreSQL. If you use another DBMS, this answer isn't very useful. I sorry if my english is too rough, but isn't my mother language. Cheers. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
