Received: from server1.ppc.pims.org ([194.78.114.4]) by hub.org (8.9.3/8.9.3) with ESMTP id FAA13115; Tue, 12 Oct 1999 05:52:59 -0400 (EDT) (envelope-from huffmana@ppc.pims.org) Received: from ppc.pims.org ([207.176.11.63]) by server1.ppc.pims.org (Netscape Messaging Server 3.5) with ESMTP id AAA14D7; Tue, 12 Oct 1999 11:51:36 +0200 Message-ID: <3803046A.CE172801@ppc.pims.org> Date: Tue, 12 Oct 1999 11:50:35 +0200 From: "Allan Huffman" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-interfaces@postgresql.org, pgsql-hackers@postgresql.org, boulangj@ppc.pims.org, randolpf@ppc.pims.org Subject: HELP - Accessing SQL_ASCII from Java Content-Type: multipart/alternative; boundary="------------BED33262DDBAC34C3B8B3F16" --------------BED33262DDBAC34C3B8B3F16 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit 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 --------------BED33262DDBAC34C3B8B3F16 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit  
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
 
  --------------BED33262DDBAC34C3B8B3F16--