Maybe this conversation should be about how support for databases get implemented.
I have always wondered if MDG’s full stack DB approach is the best way to go instead of adopting a database language like LINQ or similar that de-couples the query language from the underlying database implementation.
While not perfect, one nice benefit of this approach might be that an app could target different backends based on unique repository features.
You might also rethink whether the client and server DBs necessarily have to be the same. Not sure if that would be good or bad.
I know I am glossing over some serious implementation details (so don’t shoot me) but I guess the question is “where do you want the complexity?”
Treating each DB as a full stack affair vs separating the DB implementation from the backend repository.
I sense some urgency from the community for MDG to support DBs other than Mongo and Redis, something relational. MySql, Sql Server, Oracle etc.
Was just pondering how building a separate full stack for each would be faster or easier to get to this end game vs building this common query language translation layer.
Just a thought.