JonnyPooleQlik
commented
10 months ago Hello -
I think you need to disable bulk reader on the connection.
It’s enabled by default in recent versions, however it cannot handle large strings like the XML blocks found in the NP repository.
“ While we believe that most customers will want all their ODBC connections to use this new capability, it is possible to turn off the Bulk Reader feature for a particular connector. To do this, add the parameter useBulkReader with a value of False to the Advanced section of the connector properties window”
Sent from my iPhone
On Sep 29, 2023, at 12:21 PM, OOsiemo @.***> wrote:
When loading the "entities_xml" FROM "nprinting"."public"."report" table, the SQL SELECT statement only loads a maximum of 255 characters instead of the full contents of that XML column. As a result, the subsequent data transformations down the line based on that initial "entities_xml" column fail. For instance, have a look at these two screenshots (where SQL SELECT statement for "entities_xml" only loads a maximum of 255 characters while the actual length of the same "entities_xml" using pgAdmin is 1,782 characters) for the same report [entities_xml column from NP Governance Dashboard]https://user-images.githubusercontent.com/146464686/271660392-2fd25e89-e680-491c-86af-f98b59b44714.PNG [entities_xml column from pgAdmin4]https://user-images.githubusercontent.com/146464686/271660396-8f8b3133-0e52-43df-9b88-285aa291a5b9.PNG
So in a sense, it seems that the SQL SELECT statement treats that column as a normal ASCII with max 255 characters. Is there a way to treat it as an XML construct instead? By the way, I am using the latest version of NPrinting i.e. May 2023 SR1 (v23.20.3)
— Reply to this email directly, view it on GitHubhttps://github.com/eapowertools/NPrintingGovernanceDashboard/issues/11, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQLC3IEHUMI7L7S6DQGH5DDX43YOTANCNFSM6AAAAAA5MWLXEQ. You are receiving this because you are subscribed to this thread.Message ID: @.***>
The information transmitted by Qlik is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Qlik's Privacy & Cookie Noticehttps://www.qlik.com/us/legal/privacy-and-cookie-notice describes how we handle personal information
The information transmitted by Qlik is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Qlik's Privacy & Cookie Noticehttps://www.qlik.com/us/legal/privacy-and-cookie-notice describes how we handle personal information
OOsiemo
When loading the "entities_xml" FROM "nprinting"."public"."report" table, the SQL SELECT statement only loads a maximum of 255 characters instead of the full contents of that XML column. As a result, the subsequent data transformations down the line based on that initial "entities_xml" column fail. For instance, have a look at these two screenshots (where SQL SELECT statement for "entities_xml" only loads a maximum of 255 characters while the actual length of the same "entities_xml" using pgAdmin is 1,782 characters) for the same report
So in a sense, it seems that the SQL SELECT statement treats that column as a normal ASCII with max 255 characters. Is there a way to treat it as an XML construct instead? By the way, I am using the latest version of NPrinting i.e. May 2023 SR1 (v23.20.3)