topic Re: DATABASE LOAD CHANGES LENGTH WHEN SWITCHING TO MEMORY (POSTGRESQL) in App Development

DATABASE LOAD CHANGES LENGTH WHEN SWITCHING TO MEMORY (POSTGRESQL)

fontesflp — Fri, 13 Jan 2023 13:07:02 GMT

My text field has a maximum size of 255 characters when loading into qlik's memory. The same field loaded in pgadmin has a longer length.

Re: DATABASE LOAD CHANGES LENGTH WHEN SWITCHING TO MEMORY (POSTGRESQL)

fontesflp — Fri, 13 Jan 2023 17:41:04 GMT

I solved the problem.
For some reason, when the column is of type TEXT, the qlik LOAD only loads 255 characters.
By changing the type to CHARACTER VARYING(1000), the LOAD loads the complete string

Re: DATABASE LOAD CHANGES LENGTH WHEN SWITCHING TO MEMORY (POSTGRESQL)

obmk — Tue, 21 Feb 2023 15:24:22 GMT

In addition to this solution, the following tip might also be helpful in this context when it's about

"extracting data from TEXT columns having much more than 1000 or 16384 characters inside":

https://community.qlik.com/t5/App-Development/Does-column-length-in-SQL-SF-table-matter-when-reading-data-into/m-p/2040442/highlight/true#M85726

so short

Stefan

Re: DATABASE LOAD CHANGES LENGTH WHEN SWITCHING TO MEMORY (POSTGRESQL)

amon — Tue, 04 Jul 2023 21:19:29 GMT

You saved my life, I had the same issue with the same use case (polyline geometries), works as a charm