com.mysql.jdbc.MysqlDataTruncation: Data truncation: Truncated incorrect DOUBLE value:

-
This error may crop up if you are doing any DML operation through IN clause.
Example
String sql = 'update table set status = true where id in (?)'

If you are using the above statement as part of the prepared statement and the 'id' column is of long type. Following would give this error.
String str = "1,2,3,4";

PreparedStatement stmt = connection.prepareStatement(sql);
stmt.setString(1, str);
stmt.executeUpdate();

The last line would give the error.
Reason being that the column is of Long(BIGINT) type and value is passed as string.
You cannot say
stmt.setLong(1, str);
as the 'str' contains comma separated values.
One of the solution in this case is to create separate place holders for each input value
String sql = 'update table set status = true where id in (?,?,?,?)'
in this case and pass individual long values to the statement object.

Other options are welcome.

Comments

Post a Comment

Popular posts from this blog

Hibernate: a different object with the same identifier value was already associated with the session

-
People working with Hibernate might be familiar with the below error. org.springframework.orm.hibernate3.HibernateSystemException: a different object with the same identifier value was already associated with the session: nested exception is org.hibernate.NonUniqueObjectException: a different object with the same identifier value was already associated with the session This exception is generated when we try to load an instance object in session which has been already loaded by hibernate. Easier said than done. Hibernate considers two persistent entities identical if the two rows of the table can be said identical. Above error could be generated in many ways and there may be various solutions on net like using session merge etc to get away with the problem. I will discuss here the reason for me getting this problem and the way I resolved it. Below is the code which generated the exception for me. Following is the method which caused the exception @Transactional(propagation=Propagation.
Read more

BeanDefinitionStoreException: Failed to parse configuration class: Could not find class [javax.jms.ConnectionFactory]

-
If you are creating a Spring Boot application and see the following error stack . ____ _ __ _ _ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ \\/ ___)| |_)| | | | | || (_| | ) ) ) ) ' |____| .__|_| |_|_| |_\__, | / / / / =========|_|==============|___/=/_/_/_/ :: Spring Boot :: (v2.2.0.RELEASE) 2020-06-27 19:30:32.786 INFO 35224 --- [ main] SchoolApplication : Starting SchoolApplication on LTUS76179 with PID 35224 (C:\personal\eclipse-workspace\apievolution\target\classes started by 381548 in C:\personal\eclipse-workspace\apievolution) 2020-06-27 19:30:32.796 INFO 35224 --- [ main] SchoolApplication : No active profile set, falling back to default profiles: default 2020-06-27 19:30:32.964 WARN 35224 --- [ main] ionWarningsApplicationContextInitializer : ** WARNING ** : Your ApplicationContext is unli
Read more