Brian Sutherland wrote:
On Thu, Mar 30, 2006 at 04:22:50PM +0400, Dmitry Vasiliev wrote:
Ok, I'll try to synchronize all my ideas about 'zope.app.rdb' with Stuart for a
proposal.
Just a random thought, so don't shoot me if it's a bad one. Perhaps it
can be moved out of zope.app at the same tim
On Thu, Mar 30, 2006 at 04:22:50PM +0400, Dmitry Vasiliev wrote:
> Ok, I'll try to synchronize all my ideas about 'zope.app.rdb' with Stuart for
> a
> proposal.
Just a random thought, so don't shoot me if it's a bad one. Perhaps it
can be moved out of zope.app at the same time?
--
Brian Suther
Stuart Bishop wrote:
I think I know what might have been going on. The earlier patch neglected to
change getEncoding() to always return UTF-8. So the code in zope.app.rdb
that encodes the queries was encoding them to whatever getEncoding()
happened to return rather than UTF8.
Ugh, I guess I've
Stephan Richter wrote:
On Tuesday 28 March 2006 08:09, Dmitry Vasiliev wrote:
The getEncoding() approach isn't meaningful with database adapters that
accept Unicode strings which is becoming the norm. The idea that database
adapters will never be Unicode aware seems to have been embedded into Z3
On Tuesday 28 March 2006 08:09, Dmitry Vasiliev wrote:
> > The getEncoding() approach isn't meaningful with database adapters that
> > accept Unicode strings which is becoming the norm. The idea that database
> > adapters will never be Unicode aware seems to have been embedded into Z3
> > quite dee
Stuart Bishop wrote:
[moving to zope3-dev]
I think I know what might have been going on. The earlier patch neglected to
change getEncoding() to always return UTF-8. So the code in zope.app.rdb
that encodes the queries was encoding them to whatever getEncoding()
happened to return rather than UTF
