HELP - Accessing SQL_ASCII from Java

From: "Allan Huffman" <huffmana(at)ppc(dot)pims(dot)org>
To: pgsql-interfaces(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org, boulangj(at)ppc(dot)pims(dot)org, randolpf(at)ppc(dot)pims(dot)org
Subject: HELP - Accessing SQL_ASCII from Java
Date: 1999-10-12 09:50:35
Message-ID: 3803046A.CE172801@ppc.pims.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-interfaces


Dear Fellow Developers and Hackers,

After installing PostgreSQL 6.5.2 (on my Sparc 7) and configured as
follows:
“--with-mb=UNICODE”

I am getting a truncation of some varchar columns. When accessing a
PostgreSQL table1. I get this error in my postmaster window:

“ERROR: Conversion between UNICODE and SQL_ASCII is not supported”

And this error in my DOS window (which Visual Café Database Edition uses
to run applets from):

“The maximum width size for column 2 is: 17”

table1:
+------------------------------------------------+
! Field ! Type ! Length !
+------------------------------------------------+
! data_code ! varchar() ! 15 !
! data_field ! varchar() ! 43 !
+------------------------------------------------+

>From my PC Java GUI, running in Visual Café, I am able to enter a full
15 character string into data_code but I get the following error when I
try to enter a 43 (or greater than 17) character string into data_field:

“Invalid value for the column data”

and it truncates the data I enter to 17 characters.

>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!

+__________________________________________________________________________+

Without UNICODE configured I got the following errors:

>From the Postmaster:

"ERROR: MultiByte strings (MB) must be enabled to use this function."

>From Visual Café:

"The maximum width size for column 2 is: 17"

+__________________________________________________________________________+

Any suggestion will be greatly appreciated, even a work around. What I
want to do is just access SQL_ASCII and leave UNICODE alone!

Sincerely,

Allan

Browse pgsql-hackers by date

  From Date Subject
Next Message Horak Daniel 1999-10-12 10:08:48 win32 port on newer Cygwin snapshots (990115)
Previous Message Tatsuo Ishii 1999-10-12 09:32:15 Re: [HACKERS] Different BLKSZ

Browse pgsql-interfaces by date

  From Date Subject
Next Message Israel Zavalza Bahena 1999-10-12 13:22:03 Re: [INTERFACES] Postgres ODBC and PostgreSQL 6.5.2
Previous Message Jan Wieck 1999-10-12 09:12:11 Re: Scripts (was Re: [HACKERS] Re: [INTERFACES] Next release is