RE: Bind Parameter is Too Big

After working between Appeon for Powerbuilder and SAP for Sybase ASE 15.7, I finally figured out the issue.

In the ODBC Driver Administrator, if I configure the postgres ODBC driver and go to Datasource, the Max Varchar limit
is255 by default. I changed this to 1000 and now everything works. 

I will note, during my testing with Appeon, I discovered via DBtrace that all of my varchar columns report with twice
thelength of the actual amount a characters in them, when piping from Sybase ASE 15.7 to Postgres. Appeon experienced
thesame thing, but didn't have an explanation. SAP didn't have an explanation either. 


-----Original Message-----
From: Tom Lane <tgl@sss.pgh.pa.us>
Sent: Thursday, September 01, 2022 4:03 PM
To: Kluzak, Matthew C. <mckluzak@nd.gov>
Cc: Adrian Klaver <adrian.klaver@aklaver.com>; pgsql-general@lists.postgresql.org
Subject: Re: Bind Parameter is Too Big

***** CAUTION: This email originated from an outside source. Do not click links or open attachments unless you know
theyare safe. ***** 

"Kluzak, Matthew C." <mckluzak@nd.gov> writes:
> The Sybase databases use

> Character Set = 1, iso_1
>     ISO 8859-1 (Latin-1) - Western European 8-bit character set.
> Sort Order = 50, bin_iso_1
>     Binary ordering, for the ISO 8859/1 or Latin-1 character set (
>     iso_1).

> The Postgres database uses UTF8

Hmmm ... it's plausible that something somewhere is figuring that
ISO-8859-1 conversion to UTF8 could expand the data at most 2X, and that's where the 1000-to-2000 multiplier is coming
from.

I wonder if it would help to set things up so that the client side is sending ISO-8859-1 to Postgres (ie,
client_encoding= latin1) and the encoding conversion happens on the server side. 
In principle it shouldn't matter where the conversion happens, but you might be dealing with some bug or
underdocumentedlimitation in whatever is doing that conversion on the client side. 

                        regards, tom lane

________________________________
This transmission, email and any files transmitted with it, may be: (1) subject to the Attorney-Client Privilege, (2)
anattorney work product, or (3) strictly confidential under federal or state law. If you are not the intended recipient
ofthis message, you may not use, disclose, print, copy or disseminate this information. If you have received this
transmissionin error, notify the sender (only) and delete the message. This message may also be subject to disclosure
underthe North Dakota Open Records Laws.