kw123

I am asking this question as I am developing a data access solution that will change the data access development into SQL development, but requires the above tools. Thanks.

If you prefer SQL, what are the ideal features you wish to have? Like editing SQL in a SQL editor, having object-relational data transformation abstracted away, etc.

If you don't like SQL, do you prefer to have only DAO/repository interface in your application and defer the implementation to backend or even to some other people?

Overall, do you think that we need a "better" solution than ORM? For example, something that is simple but allows us to handle complex objects. I am working on a solution for relational database access and trying to get directions. Your comments are really appreciated.

I am hoping to have a prototype platform soon. It is to simplify relational data access and make persistence a backing service for microservices and serverless applications. You will specify persistence services with SQL and JSON only using a WebIDE and run them as managed services. I am uncertain how useful this is and would like to hear from you. If interested, slight more info is here: https://github.com/bklogic/backlogic-persistence. Thanks in advance.