Don't use a unicode database with postgresql versions < 8.1
...
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Ryo HAYAKAWA
> Sent: Friday, September 16, 2005 12:03 PM
> To: dbmail-dev@dbmail.org
> Subject: [Dbmail-dev] patch for postgresql to wor
Hello Paul,
From: Ryo HAYAKAWA <[EMAIL PROTECTED]>
Subject: Re: [Dbmail-dev] patch for postgresql to work in UNICODE encoding.
Date: Fri, 16 Sep 2005 18:31:18 +0900 (JST)
Message-ID: <[EMAIL PROTECTED]>
> > Would this utf-8 mode for postgres be useful as the default setup for
Hello Paul,
From: Paul J Stevens <[EMAIL PROTECTED]>
Subject: Re: [Dbmail-dev] patch for postgresql to work in UNICODE encoding.
Date: Fri, 16 Sep 2005 09:30:59 +0200
Message-ID: <[EMAIL PROTECTED]>
> Would this utf-8 mode for postgres be useful as the default setup for
&
Hello Aaron,
To be honest with you, I do not speak English well, so I got some
translation help from my co-worker. (the coworker: whats up :-)).
> Well, edit the output from diff and remove everything not related to
> your changes! It is indeed horribly annoying to dig through 50KB diffs
> becaus
Ryo HAYAKAWA wrote:
> Hi there.
>
> It was neccesary for me to run DBmail 2.1.2 on PostgreSQL database
> with UNICODE(UTF-8) charset. But, unfortunately, the UNICODE(UTF-8)
> charset did not work with it.
>
> So, I have created a patch to use the dbmail_messageblks.messageblk
> field as bytea.
On Fri, 2005-09-16 at 11:03 +0900, Ryo HAYAKAWA wrote:
> The attached file is hard to read because the size is big( it has not
> only C codes but also some configuration for DB, fixes for autoconf).
Well, edit the output from diff and remove everything not related to
your changes! It is indeed hor
