That's OK -- it just means that only one of the two possible resolutions are available for the moment. That'll change in the near future and the message will still apply just fine.
Aaron On Mon, Jun 20, 2005, ""John Hansen"" <[EMAIL PROTECTED]> said: > Only,. 8.1 is not released yet..... > >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Stone >> Sent: Tuesday, June 21, 2005 7:34 AM >> To: DBMAIL Developers Mailinglist >> Subject: RE: [Dbmail-dev] [DBMail 0000218]: invalid byte >> sequence forencoding"UNICODE" >> >> On Mon, Jun 20, 2005, ""John Hansen"" <[EMAIL PROTECTED]> said: >> >> >> >> >> Would it make sense to put a note in the PostgreSQL install >> >> instructions, or the database script or something that says not to >> >> use UNICODE? >> > >> > This has been fixed in PostgreSQL 8.1 >> >> In that case I'd be happier bombing with an error message that says: >> >> "Your PostgreSQL version is less than 8.1 and has been >> configured with CHARSET=UNICODE. This is not supported by >> DBMail. Please change to CHARSET=ASCII or upgrade to >> PostgreSQL 8.1 or above." >> >> Aaron >> _______________________________________________ >> Dbmail-dev mailing list >> Dbmail-dev@dbmail.org >> http://twister.fastxs.net/mailman/listinfo/dbmail-dev >> >> > _______________________________________________ > Dbmail-dev mailing list > Dbmail-dev@dbmail.org > http://twister.fastxs.net/mailman/listinfo/dbmail-dev > --
