Thanks for the quick response! I've been looking through the linked project, I see a similar relationship between customer and subcart. But it seems a little counter intuitive to me. If a purchase is composed of subpurchases, my natural approach would be to define a purchase object with a seq of subpurchases. But if I understand the model definitions correctly, I need to do the opposite: define purchase as a field of subpurchase. I couldn't find an example of selecting subpurchases, but extrapolating from the model definition, it seems like I would select a seq of subpurchases by purchase id and pass around that sequence to whatever needed the purchase information.
I can redo my models to match the ones defined in the sample project. But here is a fully formed example of what I was expecting to work: <https://gist.github.com/nepeckman/5152f1eb93f8213782f880d666e066cb>. You said I'm defining the type relationship, but not the object relationship, and that makes sense to me. But is there a way to specify the object relationship in the DB query, and get the desired result at the end? Thanks again for the help and creating such an awesome ORM!
