This looks really helpful, I'll definitely check it when I run into problems with persistence. Which will be probably very soon - I have to admit I've been usin

This looks really helpful, I'll definitely check it when I run into problems with persistence. Which will be probably very soon - I have to admit I've been using JPA for almost a decade and I still find it so confusing that I'd rather use native SQL for any non-trivial scenario(i.e. everything above plain CRUD). N+1 select problem is far from the hardest issue with JPA, for me it's either mixing managed and detached objects or following weird cascading rules especially during updates.