The way I have done it is to ensure that truncation only happens on valid UTF-8
boundaries but length calculation is done in "use bytes" mode, and then try to
guesstimate where to make the UTF-8 cut, and try that repeatedly until you
manage to go under the max size you specified. Then you
What about truncating the data in PLSQL? Eg an insert function? It would have
to input a CLOB I would guess…
Sent from my iPhone
> On May 28, 2021, at 4:15 AM, Marcus Bergner wrote:
>
>
> The way I have done it is to ensure that truncation only happens on valid
> UTF-8 boundaries but
That would work, I think. Or, just changing the datatype in the table for the
comments to a 4K CLOB in the *first* place, then the perl side truncate would
work. This table is truncated each year, so there’s no real need to maintain
any sort of historical data.
On May 28, 2021, at 3:55 AM,
