That's a good start but ideally you'd have Query&l...

# tornadofx

[teedee]

That's a good start but ideally you'd have Query<Customer> where calling list() would be sufficient to get the list of Customer objects with the list of orders as a field. If KDBC is built with the assumption of get() handling only a single row that might be a little more complex however.