I have a query that returns CLOBs, that I split into 32767-character chunks in order to fit into Excel cells.
And I was pleased with myself for discovering the REGEXP_SUBSTR on a CLOB will return a CLOB from an SQL query whereas SUBSTR and DBMS_LOB.SUBSTR won't.
However, when I try and copy to Excel, I still get an error that some values are too large for the limit of 32767 characters.
Further investigation revealed that when the CLOB values are copied to Excel, any simple LF linebreaks are converted to Windows-style CRLF ones, which bumps up the size of the string.
Is this something I can change in the configuration? I'm using version 13 and I can't find anything that changes this behaviour.
And I was pleased with myself for discovering the REGEXP_SUBSTR on a CLOB will return a CLOB from an SQL query whereas SUBSTR and DBMS_LOB.SUBSTR won't.
However, when I try and copy to Excel, I still get an error that some values are too large for the limit of 32767 characters.
Further investigation revealed that when the CLOB values are copied to Excel, any simple LF linebreaks are converted to Windows-style CRLF ones, which bumps up the size of the string.
Is this something I can change in the configuration? I'm using version 13 and I can't find anything that changes this behaviour.
