Yep, I'm a big fan of building views in postgres and just hitting those with the ORM. I don't even use the join syntax in my ORM (Ecto) - if I need a join, I use a view.
Dynaboard shutting down does not relate to pricing for end-users.
From a Low Code product perspective, we were still able to build a beautiful and functional product. Our product unit/engineer ratio is much higher than our competition (see, for example, Retool), which allows us to provide the best value for our users. Regarding the transition, I don't see any indication from the note you posted that users will have to rebuild all their apps. Rather, the founder is saying he will provide more information and possible steps. Who knows – maybe it would be integrated into Figma? And Figma would gain great runtime and IDE capacities?
Sorry I didn't link to a Dynaboard email. Here's what an (unhappy) customer of theirs sent me: https://imgur.com/a/qTGpgbQ. They were unhappy because they're a) losing all their data, and b) losing all their applications.
mehal and I are former Dynaboard engineers, so we are well aware of the situation. No one is more upset about the removal of Dynaboard than the team, but it doesn't justify poor pricing practices from competitors
No Russian Army because he was born around 1914. Otherwise, of course you would find a lot of people with -enko last name in Russian Army in WWI. Not only Russian Empire controlled most of present-day Ukraine but also parts of Poland.
It actually does support summing up. I've discovered - it work in a groups. If you have set of queries divided by space, keyword 'total' or 'sum' would result in a sum of previous group
