Dmitry Vasiliev wrote:
> Håkan Johansson wrote:
>> On Mar 1, 2006, at 14:20, Stephan Richter wrote:
>>> On Tuesday 28 February 2006 05:29, Håkan Johansson wrote:
>>>> Since I am still a newbie to Zope3, I don't know if those settings are
>>>> the "best" choice. At least it works now.
>>> Can you make a bug collector issue for this bug? Many people have
>>> reported
>>> this already, but I think there is no issue. I do not have time right
>>> now to
>>> fix it in the trunk.
>> I have now reported the bug on
>> (
> Fixed on the trunk at revision 65716.
> Also I've fixed broken tests, added CHANGES.txt and removed "utf-8"
> encoding because it doesn't work for me. For now the only reliable way
> to set encoding is through the configuration form.

What was broken with the Unicode support? This change is a regression as the
client encoding is now stuck with whatever the default client encoding
happens to be set to on the backend and allows the situation where the DA
and the backend are attempting to talk totally different encodings.

If there is a reason you cannot communicate with your backend using UTF-8
after setting the client encoding to UTF-8, then a better approach for the
DA would be to query the client encoding and use that which avoids the
possible mismatch (although this still means people are stuck using whatever
the default encoding is on the backend).

> And I really don't like error dispatching based on the error's message,
> we need to redo error handling for psycopgda.

The only way of catching deadlock and serialization exceptions from psycopg
is by sniffing the exceptions. psycopg2 might do this for us by raising more
granular exceptions - I don't know. If it does, it will do so by sniffing
the exception messages for us because I think this is all the PostgreSQL API
gives you to work with (although thankfully the string is well documented,
at least in the case of serialization exceptions).

Stuart Bishop <[EMAIL PROTECTED]>

Attachment: signature.asc
Description: OpenPGP digital signature

Zope3-users mailing list

Reply via email to