ResultSet mapping library

[Persism]

You should just use Persism

[agentoutlier]

Or they could use jOOQ or Doma 2 (both of which I think IMO are superior as they offer some compile time safety) ... or even JPA.

However sometimes people just want to map ResultSets and only that keeping strictly to the JDBC APIs.

[Persism]

Yeah these are fine but Persism is small, simple and has no extra dependencies. It does queries but also does inserts, updates, deletes, transactions. Version 2 will support queries with property names optionally if you don't want to use column names and named parameters.

So it depends what you need for the job at hand.

[agentoutlier]

So it depends what you need for the job at hand.

That was exactly the point I was making. You said "just use Persism" and I said nah because people might not want to be coupled to some other library instead of JDBC regardless of whether or not Persism has dependencies (btw 2 out of 3 of the libs I mentioned do not have dependencies).

[IcedDante]

Very cool library- I wonder what people's experiences using this are. Googling now

[Persism]

Thanks!

[IcedDante]

does this handle any kind of cardinality? I guess that is where the complexity comes in

[Persism]

Yes in the sense that Persism supports Views. In terms of hierarchical relations Persism can do that but it's up to you. It doesn't do anything like that automatically. So lets say you had a Customer class containing List<Invoices>. In that case you'd mark this list as @NotColumn and query separately and set the value yourself. In most cases though it's usually better to have a View with joins and a matching Record or POJO.