Just FYI, I'm using pgsql 8.1.0. Kevin
On 11/10/05, K C <[EMAIL PROTECTED]> wrote: > > Thanks, I should have searched the bug db first. > > env PGCLIENTENCODING=LATIN1 dbmail-imapd > > works for me now (I need to check what I should do to deal with encoding > at client side). > > Kevin > > On 11/10/05, Robert Fleming <[EMAIL PROTECTED]> wrote: > > > > K C wrote: > > > > > > > > That makes sense. > > > > > > In 2.0.7 I inserted a check that causes DBMail to bomb out on startup > > > with a warning that the database must be US-ASCII. In 2.1.x I'd > > > like to > > > do something more clever, like change the encoding at connection time. > > > > > > > > > That said, are you suggesting that we have to build the database with > > > encoding SQL_ASCII? Is this in the doc? I hope to keep db in UTF-8 > > > as the database will be used by other apps. > > > > > > So as to change encoding at connection time, I'm not sure if I > > > understood correctly, may not work either. With database encoding as > > > UTF-8 and client encoding SQL_ASCII, the offending sql reported the > > > same error. > > > > > > > This has been discussed a couple times before. I've tried to summarize > > it here: > > > > http://www.dbmail.org/dokuwiki/doku.php?id=unicode_postgresql_database > > > > Patches exist to address it. > > > > Regards, > > Robert > > > > _______________________________________________ > > Dbmail-dev mailing list > > [email protected] > > http://twister.fastxs.net/mailman/listinfo/dbmail-dev > > > >
