On 8/14/06, Bill Thoen <[EMAIL PROTECTED]> wrote:
It does sound suspiciously like an encoding problem, but setting the cluster and database's encoding to LATIN1 (ISO-8859-1, which is a 1-byte system) should have done the trick, but it didn't. And according to the PostgreSQL documentation's section 21.2 "Character Set Support", UTF8 is actually a multi-byte system supporting up to 4 bytes per character, and its alias name is 'Unicode'. Perhaps it has to do with how my Fedora Core 4 Linux is handling the encoding in its environment.
One more thought, I noticed that I have five PostgreSQL ODBC drivers: PostgreSQL 7.03.02.00 PostgreSQL ANSI 8.01.02.00 PostgreSQL Legacy PostgreSQL Unicode 8.01.02.00 PostgreSQL (Beta) I have been using the PostgreSQL 7.03 and PostgreSQL ANSI 8.01drivers. I do not know what the differences between the drivers are, but it might be a difference between our configurations that is causing our different results. Rich -- Richard Greenwood [EMAIL PROTECTED] www.greenwoodmap.com _______________________________________________ MapInfo-L mailing list [email protected] http://www.directionsmag.com/mailman/listinfo/mapinfo-l
