alexblokh

I truly believe that you should spend 0 time migrating SQL query to code. When you design data persistence - you do it in SQL domain, when you solve business demands in data domain - you do it in SQL. When you know how to solve problem in SQL - you should straight away know how to do it with ORM ORM should embrace SQL and not hide it under the carpet. By doing that many other ORMs supply you with hidden consequences

what would be the line between headless and headfull ORM for you?

does it lay before or after schema declaration in code in the domain of ORM does it influenced be either ORM is abstracting SQL away from you or it is abstracting on top of SQL

I think the deviation had happened and due to a massive amount of different ORMs out there - there's been a shift in ORM perception. For some reason people don't expect ORM to be an "Object Relational Mapping" in the domain of SQL databases. I try to understand why.. Also people are expecting ORM to abstract away from SQL for whatever reason instead of embracing SQL.

Do we need a new ORM and why?

For some reason there're were no such thing so we did it. Please feel free to use!