pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Allan Huffman <huffmana@ppc.pims.org>
To: pgsql-interfaces@postgresql.org
Subject: SQL_ASCII Java Access
Date: Tue, 12 Oct 1999 16:27:59 +0200
Message-ID: <3803456F.FB95D478@ppc.pims.org> (raw)

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 using pg JDBC 1.1.1.x):

“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

Time is the fire in which we burn -- Star Trek




Message-ID: <3803456F.FB95D478@ppc.pims.org>
Permalink:  ../3803456F.FB95D478@ppc.pims.org/
Also on:    postgresql.org/message-id/3803456F.FB95D478@ppc.pims.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: huffmana@ppc.pims.org
  Subject: Re: SQL_ASCII Java Access
  In-Reply-To: <3803456F.FB95D478@ppc.pims.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox