Re: MaxLongVarcharSize=8190; - Mailing list pgsql-odbc

From Dave Page
Subject Re: MaxLongVarcharSize=8190;
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC9460@ratbert.vale-housing.co.uk
Whole thread Raw
In response to MaxLongVarcharSize=8190;  ("Joel Fradkin" <jfradkin@wazagua.com>)
Responses Re: MaxLongVarcharSize=8190;
List pgsql-odbc
 


From: pgsql-odbc-owner@postgresql.org [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Joel Fradkin
Sent: 21 July 2005 22:34
To: pgsql-odbc@postgresql.org
Subject: [ODBC] MaxLongVarcharSize=8190;

When I pulled my connectionstring from the dns builder I got

MaxLongVarcharSize=8190;

We had data in our SQL database in text fields longer then 8k.

When a client tried to acces that record we got an error so I upped the MaxLongVarcharSize=8190; to

MaxLongVarcharSize=18190;

This fixed the problem, but I have been told by a conulting group (PCM) that using over 8 k might be causing my errors. 

 

Err, why exactly? As far as I'm aware, that option has always worked properly.

 

I did change it back to 8k and am a bit subjective on the outcome (we still have been having issues, but not odbc related).

Does anyone know the correct settings for my connection string to use longer then 8k text fields, or do I need to divide the data across multiple records? 

 

Set it to whatever you need. iirc, you can also use -4 (SQL_NO_TOTAL) if you like.

 

Regards, Dave.

pgsql-odbc by date:

Previous
From: "Joel Fradkin"
Date:
Subject: MaxLongVarcharSize=8190;
Next
From: "Dave Page"
Date:
Subject: Re: Blank varchar and text fields