github/jooq
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[jOOQ/jOOQ#13217] Work around xerial SQLite driver's Clob behaviour when

Browse Source 
data is null
This commit is contained in:
Lukas Eder 2022-03-07 11:17:22 +01:00
parent 7dab18c340
commit fc08adfabd
1 changed files with 10 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
jOOQ/src/main/java/org/jooq/impl/ClobBinding.java
View File

@ -41,6 +41,7 @@ import static org.jooq.impl.DefaultExecuteContext.localConnection;
import static org.jooq.impl.DefaultExecuteContext.localTargetConnection;
import static org.jooq.impl.Tools.asInt;
import java.io.Reader;
import java.sql.Clob;
import java.sql.SQLException;
import java.sql.Types;
@ -139,9 +140,16 @@ public class ClobBinding implements Binding<String, String> {
// [#13144] Cannot call Clob::length in Firebird
case FIREBIRD:
return Source.of(clob.getCharacterStream()).readString();
default:
// [#13217] The Clob may be non-null, yet the data is still null in SQLite
case SQLITE: {
Reader r = clob.getCharacterStream();
return r == null ? null : Source.of(r).readString();
}
default: {
return clob.getSubString(1, asInt(clob.length()));
}
}
}