Here is an example of the query I’m trying to execute and the POJO I’m trying to populate.
public Optional<TeacherWithStudents> getTeachersWithStudentsForStudentId(long studentId) {
return ctx().select(
TEACHER.ID,
TEACHER.NAME,
DSL.field("student.ids", STUDENT_TEACHER_MAPPING.STUDENT_ID.getDataType().getArrayType()))
.from(TEACHER)
.leftJoin(DSL.lateral(
DSL.select(DSL.arrayAgg(STUDENT_TEACHER_MAPPING.STUDENT_ID).as("ids"))
.from(STUDENT_TEACHER_MAPPING)
.where(STUDENT_TEACHER_MAPPING.TEACHER_ID.eq(TEACHER.ID))).as("student"))
.on(DSL.condition(true))
.limit(1)
.fetchOptionalInto(TeacherWithStudents.class);
}
// TeacherWithStudents class
@Data
@AllArgsConstructor
public class TeacherWithStudents {
long id;
String name;
Long[] ids;
}
Disclaimer: The query above is simplified to just the bare elements required to illustrate the problem. The real query joins on additional tables and references those tables in the where clause. If anyone is going to propose a completely different technique, please make sure it accommodates fetching multiple arrays of ids related to TEACHER with corresponding where/and clauses.
I have tried many different variations including
-
passing Long[].class to DSL.field i.e.
DSL.field("student.ids", Long[].class)
-
This works when I fetch into a record, but not my own pojo
-
I just get the following error:
Caused by: org.jooq.exception.MappingException: An error occurred when mapping record to class [Ljava.lang.Long;
-
Using DSL.jsonArrayAgg in place of DSL.arrayAgg in the hope that the jackson converter would take over as it does for similar use cases using multiset. In this case, I get an array with a single null value i.e. [null]
-
I have attempted to use multiset in the SELECT clause which works, but then I’m doing the same correlated sub-query in the SELECT and in the JOIN to enable the where condition at the bottom
-
I have tried a few variations of custom converters, but I can’t get one to work.
-
I have tried fetching the Record, calling
intoMap()
and then using jackson to write to the pojo. This works, but is wasteful.
Based on what I’ve read, it’s expected that the more complex Collection classes e.g. Set<>, List<> are not directly supported (those were my first attempts) except when using multiset because of type erasure. That makes sense, but I am surprised I can’t get Long[].class to work. I have tried dozens of variations. Often, I can get the data to populate to a Long[] if I fetch into a Jooq record, but I can never get it to populate all the way to my defined POJO. I considered giving up and just writing a custom converter from record to POJO, but it seems like this is something that should be possible. I’m convinced I’m doing something wrong.
2
Answers
This is always embarrassing, but I solved the problem simply by changing the name in the select clause. I was using
students.student_ids
and assuming that the mapper would correctly map to thestudentIds
field in the POJO. This is not the case. I changed it to reference onlystudent_ids
and it works as expected.Here is the final code
The
DSL.field("student.ids", Long[].class)
variant should work, but you have to use it twice, also in that where clause:See the
Field::contains
Javadoc. The operator by default works on string types. If jOOQ doesn’t know that the left operand is an array type, then it will use the string semantics by default. You have to tell jOOQ. The reason why you’re getting arrays containingnull
values might be just that you’re running a wrong query.Note that
DSL.field("student.ids", STUDENT_TEACHER_MAPPING.STUDENT_ID.getDataType().array())
might be more formally correct, in case you ever change data types.