Dataset export as insert statements also for CLOB column

Oh, good idea, @juergen.rausch Juergen. That should help.

I think it will still be possible to get a line longer than 2500 chars though, if the clob data has lots of line feeds....because right now, I am taking 2000 character chunks of CLOB data and then substituting CHR(13) and CHR(10), and concatenating that with ||.

If the CLOB has an XML or a JSON retreived from some REST request, it might be "pretty", meaning many linefeeds. If you make a CHR(10)||CHR(13)||' ... enough times, then the length of the line, that at the end would insert 2000 bytes, can grow quite a lot. In my case, some of these lines have the length of 3500+ bytes.

A clob formatted like following example has a lot of overhead.

{
 { 
   "name":value",
   "name":value"
.
.
.
  }
}

In my case, I get CHR(13)||CHR(10)|| put in 465 times, adding an average of almost 1200 bytes per line.

OK, got it! The big CLOB I've tested it with contains XML with no linefeeds as it is written and read only by automatic processes. So no need to make it human readable with linefeeds :wink:

Then of course it should be 2000 chars including the CHR(10/13) substitution.