Hi all, A bug reporter is suggesting that we change the dbPostgres.py to include two lines of code dealing with unicode that use the psycopg2 extensions (used only for python 2.x). The extensions deal directly with unicode issues. Apparently adding the extensions fixed an issue he was having with unicode. The problem of course is I don't know that the lines are needed and what effect they will have on existing code.
I'm on Linux, python 2.7 and postgres 9.1. When I play around with unicode (at least what I think is unicode - spanish) I do NOT see an issue. Of course all three items Linux, Python and Postgres use UTF8. BTW I'm under the impression that UTF8 = UNICODE. So from my POV I don't see an need. I know that several issues have come to light for other databases and that others have struggled with unicode. But to be honest I don't know much about it. And to be really honest I doubt I'd be able to test encoding. I'm under the impression that the keyboard setup (along with other settings) have to be changed. So is there someone (who also using postgres) on the list willing to play with this issue. Johnf _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
