Looking yet further at
ERROR: conversion between latin9 and LATIN1 is not supported
mulitbyte.c looks as though it needs the included patch, because
support for WIN1252 encoding was added to the server on 2005/03/14
so was released with 8.1 (2005/11/08), and because latin9 is a
worse match for win1252 than latin1.
e.g., your windows client with win1252 sends a 1/2 character, 0xbd to
a 8.1 server. The odbc code says 8.1>=7.1, I'll send 0xbd as latin9.
But, 0xbd in latin9 is oe. 0xbd in latin1 is 1/2 and what you would
Some might say "ah but the euro symbol which exists in win1252 exists
in latin9 but not in latin1". OK, but I would you represent it?
In win1252, euro is 0x80. Send 0x80 as latin1 or latin9, get nothing -
it's in the 0x80-0x9f control character range.
pgsql-odbc by date
|Next:||From: Sistemas C.M.P.||Date: 2006-05-05 15:18:09|
|Subject: postgres and crystal reports|
|Previous:||From: Philippe Lang||Date: 2006-05-04 13:04:58|
|Subject: PGSQL NOTICE messages through ODBC / ADO?|