<br />Dear Fellow Developers and Hackers, <p>After installing PostgreSQL 6.5.2 (on my Sparc 7) and configured as
follows:<br /><b>--with-mb=UNICODE</b><p>I am getting a truncation of some varchar columns. When accessing a
PostgreSQL <b>table1</b>. I get this error in my postmaster window: <p><b>ERROR: Conversion between UNICODE and
SQL_ASCIIis not supported</b><p>And this error in my DOS window (which Visual Café Database Edition uses to run
appletsfrom):<b></b><p><b>The maximum width size for column 2 is: 17</b><p><b>table1</b>: <br
/><tt>+------------------------------------------------+</tt><br/><tt>! Field ! Type ! Length
!</tt><br/><tt>+------------------------------------------------+</tt><br /><tt>! <b>data_code</b> !
varchar() ! 15 !</tt><br /><tt>! <b>data_field</b> ! varchar() ! 43 !</tt><br
/><tt>+------------------------------------------------+</tt><p>Frommy PC Java GUI, running in Visual Café, I am able
toenter a full 15 character string into <b>data_code</b> but I get the following error when I try to enter a 43 (or
greaterthan 17) character string into <b>data_field</b>: <p><b>Invalid value for the column data</b><p>and it
truncatesthe data I enter to 17 characters. <p>From a psql prompt on the same Sun that is running the postmaster I can
change(select) the table without the truncation and no mention of UNICODE!
<p>+__________________________________________________________________________+<p>Without UNICODE configured I got the
followingerrors: <p>From the Postmaster: <p><b>"ERROR: MultiByte strings (MB) must be enabled to use this
function."</b><p>FromVisual Café: <p><b>"The maximum width size for column 2 is:
17"</b><p>+__________________________________________________________________________+<p>Any suggestion will be greatly
appreciated,even a work around. What I want to do is just access SQL_ASCII and leave UNICODE alone! <p>Sincerely,
<p>Allan<br /> <br />
