Skip to main content
Announcements
MAINTENANCE ALERT: Dec. 12th starting 9 AM CET. Community will be read-only. GET DETAILS

Qlik Sense PosgreSql connector cut off strings containing more than 255 characters

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Andrea_Bertazzo
Support
Support

Qlik Sense PosgreSql connector cut off strings containing more than 255 characters

Last Update:

Sep 29, 2023 1:58:05 AM

Updated By:

Sonja_Bauernfeind

The native Qlik PostgreSql connector (ODBC package) does not import strings with more of 255 characters. Such strings are just cut off, the following characters are not shown in the applications. No warnings are thrown during the script execution.

The problem affects the Qlik connector but not all the DNS drivers.

 

Environment

Qlik Sense February 2023 and higher versions
Qlik Cloud

 

Resolution

When setting up the PostgreSQL connection, set the parameter TextAsLongVarchar  with value 1 in the connector Advanced settings.

TextAsLongVarChar.png

When TextAsLongVarchar is set, and the Max String Length is set to 4096, 4096 characters are loaded. 

Notice that there still are limitations to this functionality related to the datatype used in the database. Data types like text[] are currently not supported by Simba and they are affected by the 255 characters limitation even when the TextAsLongVarchar parameter is applied.

Qlik has opened an improvement request to Simba to support them.

As workaround, it is possible to test a custom connector using a DSN driver to deal with these data types.

 

Internal Investigation ID

QB-21497

Labels (1)
Version history
Last update:
‎2023-09-29 04:58 AM
Updated by: