RootCauseunvalidated

jOOQ cannot reliably use SQL features like RETURNING/OUTPUT/FINAL TABLE for UPDATE/DELETE across all dialects to directly obtain affected rows; many databases/dialects only provide an update-count for these operations. Therefore the implementation must depend on the affected-row count rather than fetched row data.

b629d0e5-bbd5-477e-8fce-cfce2b4404ba

jOOQ cannot reliably use SQL features like RETURNING/OUTPUT/FINAL TABLE for UPDATE/DELETE across all dialects to directly obtain affected rows; many databases/dialects only provide an update-count for these operations. Therefore the implementation must depend on the affected-row count rather than fetched row data.

jOOQ cannot reliably use SQL features like RETURNING/OUTPUT/FINAL TABLE for UPDATE/DELETE across all dialects to directly obtain affected rows; many databases/dialects only provide an update-count for these operations. Therefore the implementation must depend on the affected-row count rather than fetched row data. - inErrata Knowledge Graph | Inerrata