Re: [Pypgsql-users] Re: [ANN] pyPgSQL 2.1 released

[Adam B. <ad...@po...>]

> I've fiddled with adding Unicode support for some time now, but I didn't get
> enough testers yet to make me comfortable enough with it for adding it to a
> pyPgSQL release. On the Sourceforge patches section, I've uploaded a patch for
> full Unicode support, including getting Unicode results back from the database,
> insert Unicode strings, and automatic encoding conversions. I'll try to update
> this patch today to work with the latest pyPgSQL 2.1 release and drop you a
> note when it's ready.

I'm very, very sorry I haven't find time yet for testing your Unicode
patch yet :(((  I know that You made a huge effort to bring this
functionality to pyPgSQL and that I should have help You at least with
testing it.  I hope I will manage to do this within two or three days,
but I cannot promise anything, I'm afraid.

I'd like also to ask, why is it still necessary to set the encoding
twice, one time during connect() (as a "client_encoding" parameter),
and the second one using "set client_encoding to ..." command?  Why
doesn't pyPgSQL send this command to PostgreSQL automatically?  Is it
something I don't understand here? :)

-- 
Adam Buraczewski <ad...@po...> * Linux registered user #165585
GCS/TW d- s-:+>+:- a- C+++(++++) UL++++$ P++ L++++ E++ W+ N++ o? K? w--
O M- V- PS+ !PE Y PGP+ t+ 5 X+ R tv- b+ DI? D G++ e+++>++++ h r+>++ y?