I can confirm this: my application happily inserts CLOB data well over the 32K
using JPA
On Mar 24 2023, at 5:38 am, Stanimir Stamenkov via derby-user
wrote:
> Thu, 23 Mar 2023 14:54:50 -0600, /Russell Bateman/:
>
> > In fact, experimentation seems to suggest that the breaking point is a
> >
On 24/03/2023 07:38, Stanimir Stamenkov via derby-user wrote:
Thu, 23 Mar 2023 14:54:50 -0600, /Russell Bateman/:
In fact, experimentation seems to suggest that the breaking point is a
length of 32K+.
This seems to match the VARCHAR and LONG VARCHAR specifications:
*
Late yesterday afternoon, I hit upon the idea of inserting a '?' where
the CLOB would be, then using PreparedStatement to satisfy it. *This
worked and I'm able to insert even 20Mb-long rows*:
final String INSERT_CLOB = "INSERT INTO ... ? ...)"; Clob clob =
connection.createClob();
On 24/03/2023 16:33, Russell Bateman wrote:
Late yesterday afternoon, I hit upon the idea of inserting a '?' where
the CLOB would be, then using PreparedStatement to satisfy it. *This
worked and I'm able to insert even 20Mb-long rows*:
Yes, the limit is purely a limit on the length of string
On 24/03/2023 16:33, Russell Bateman wrote:
Late yesterday afternoon, I hit upon the idea of inserting a '?' where
the CLOB would be, then using PreparedStatement to satisfy it. *This
worked and I'm able to insert even 20Mb-long rows*:
And you know what, you should always do this anyway to
