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

[jOOQ/jOOQ#17203] NPE while reading timestamp data type value for SAP SQL Anywhere 17 with jconn4

Browse Source
This commit is contained in:
Lukas Eder 2024-09-09 12:39:14 +02:00
parent ca9e7a311d
commit 40ed55fbdc
1 changed files with 29 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

50
jOOQ/src/main/java/org/jooq/impl/MetaDataFieldProvider.java
View File

@ -130,30 +130,38 @@ final class MetaDataFieldProvider implements Serializable {
DataType<?> dataType = SQLDataType.OTHER;
String type = meta.getColumnTypeName(i);
try {
dataType = DefaultDataType.getDataType(
configuration.family(),
type,
precision,
scale,
!FALSE.equals(configuration.settings().isForceIntegerTypesOnZeroScaleDecimals())
);
// [#17203] jconn4 has a bug here where for some data types (e.g. timestamp), it doesn't return anything
if (type != null) {
try {
dataType = DefaultDataType.getDataType(
configuration.family(),
type,
precision,
scale,
!FALSE.equals(configuration.settings().isForceIntegerTypesOnZeroScaleDecimals())
);
if (dataType.hasPrecision())
dataType = dataType.precision(precision);
if (dataType.hasScale())
dataType = dataType.scale(scale);
if (dataType.hasPrecision())
dataType = dataType.precision(precision);
if (dataType.hasScale())
dataType = dataType.scale(scale);
// JDBC doesn't distinguish between precision and length
if (dataType.hasLength())
dataType = dataType.length(precision);
// JDBC doesn't distinguish between precision and length
if (dataType.hasLength())
dataType = dataType.length(precision);
}
// [#650, #667] All types should be known at this point, but in plain
// SQL environments, it is possible that user-defined types, or vendor-specific
// types (e.g. such as PostgreSQL's json type) will cause this exception.
catch (SQLDialectNotSupportedException e) {
if (log.isDebugEnabled())
log.debug("Not supported by dialect", e.getMessage());
}
}
// [#650, #667] All types should be known at this point, but in plain
// SQL environments, it is possible that user-defined types, or vendor-specific
// types (e.g. such as PostgreSQL's json type) will cause this exception.
catch (SQLDialectNotSupportedException e) {
log.debug("Not supported by dialect", e.getMessage());
else {
if (log.isDebugEnabled())
log.debug("No type name is available at column index: " + i);
}
fields[i - 1] = field(name, dataType);