Hi,

I use Hibernate 5.2.10 and ojdbc8 and try use clob in SQLQuery option.

In hibernate it works, but the Database gives error because a string of more than 4000 characters arrives instead of a clob.

By prepareStatment works by what will not be the OJDBC, Hibernate remains.

Anyone have an idea of what it might be?

We have a ClobTest that runs just fine with Oracle and ojdbc8.

Now, there are two situataions for that issue:

1. Either you don't select a Clob column, but a VARCHAR one.
2. Or, you select a Clob as a String so the StringType is used instead of ClobType.

Therefore, you need to add the add:

1. The table schema for the query in question
2. The entity mapping for the table
3. The query that fails

We use this code:

Clob clob = hbCtx.getConnection().createClob();
clob.setString(text)
query.setParameter(paramsVal[0], clob, StandardBasicTypes.CLOB);

But try others.

Note:
Query query = createNativeQuery(stringQuery);

What if you try like this:



What exactly is the paramsVal[0]? Is it the name of the param or some index?

I try this tomorrow.

The paramsVal[0] it's a paramName that we receive in AM array.

Thanks.

These code doesn't work. We get the same problem:

Caused by: java.sql.SQLException: ORA-01460

In that case, you need to debug your own test and compare it with ours and see why your test does not work while ours works just fine.

In your test is used HQL anda I user SqlQuery.

In Query (hql) work fine.

In that case, you can enable JDBC logging, get the query Hibernate executes and use it for your native query.

Yes, I user logging and the query is correct.

The problem is that I use a CLOB and setParameter as a ClobType, but when execute in Oracle the type is a VARCHAR2.

When have less than 4000 chars work, when it's bigger give an error.

The problem exist in NativeQuery or SQLQuery (in 4.1) and the JDBC that send a wrong type to DB.

The problem is that 4.x is no longer maintained. Check out if it works with 5.2 or 5.1, and, if it works, then it's time for an upgrade.

I have the same problem um 4.1 and the 5.2

If you can replicate it on 5.2 using our test case templates, then you should open a Jira issue.