9. Receiving Results
General usage: 9. Receiving Results. Status links explain differences for each data source.
| Data source | Row mapping | Row callbacks | Result extraction |
|---|---|---|---|
| MySQL | ✓ Supported | ✓ Supported | ✓ Supported |
| PostgreSQL | ✓ Supported | ✓ Supported | ✓ Supported |
| Oracle | ✓ Supported | ✓ Supported | ✓ Supported |
| SQL Server | ✓ Supported | ✓ Supported | ✓ Supported |
| DB2 | ✓ Supported | ✓ Supported | ✓ Supported |
| H2 | ✓ Supported | ✓ Supported | ✓ Supported |
| ClickHouse | ✓ Supported | ✓ Supported | ✓ Supported |
| Redis | ◐ Partial | ◐ Partial | ◐ Partial |
| MongoDB | ✓ Supported | ✓ Supported | ✓ Supported |
| ES 6 | ✓ Supported | ✓ Supported | ✓ Supported |
| ES 7 | ✓ Supported | ✓ Supported | ✓ Supported |
| Milvus | ✓ Supported | ✓ Supported | ✓ Supported |
- API entry points: Programmatic API, Mapper API (method annotations), Builder API, and Mapper files.
- Partial support: follow the status link to see which entry points are available. An unavailable query entry point does not mean a handler cannot process the result.
- Row mapping: use
RowMapperto map each row to an object. - Row callbacks: use
RowCallbackHandlerto consume rows individually. - Result extraction: use
ResultSetExtractorto process a result set; built-in extractors also provide filtering, pairs, and other operations.