PhilippMDoerner

@moigagoo Could you tell me whether you'd want such a feature? I have my own solution for this already with nisane, so I wouldn't want to go through the effort...

Nice that we have part of the problem somewhat covered! I likely should write up some docs for that or sth. However, there are 2 points I would want to...

I've got a first draft going that currently can't deal with nested objects because hot damn do I not get why it doesn't properly work. I think there's a copy...

@moigagoo I've settled on an implementation for the parsing of Row to arbitrary object. And I think it now comes down whether this should be in norm, some sort of...

Through merging #164 this issue is no longer necessary. We can now fire raw SQL select queries and have the output be parsed into a custom ref object type of...

Just saw this issue. I wrote myself a connection pooling package for *exactly* this: https://github.com/PhilippMDoerner/TinyPool Could it make sense to use the package in norm? Or possibly just copy paste...

In that case my first approach would likely be copy pasting the code into norm, modifying it to better integrate with norm's logging and swapping out the std/db_* libs with...

> Probably connecting Norm to an existing table. I can fully confirm that this would be the usecase, at least for me. In my case, I've got a table generated...

@moigagoo @dom96 @ajusa I think with the merging of earlier PRs from me we have passable support for one-to-many and many-to-many relationships now. You need to go through specific procs...

Turns out that's the case and I overlooked that part on the count API.