Earlier quoted context omitted.
My dream is to build a modern take of the fox/dbase family. I starting with the inner language http://tablam.org Access, as concept, is great . Is exactly what many need. But it have a lot of small deficiencies that make it disliked by developers. I have used FoxPro, and it have almost all the right things instead (Fox is Access, but goooood!... except a bit less user friendly). I wish I could dedicate to build this.…
I really like the idea of developing a modern Access alternative, but why are you trying to create a new language? Aren't QBE and SQL sufficient? Why not something that is like a cloud SaaS version of Access, but can be extended with some procedures and later used as a GraphQL backend like Hasura?
FoxPro have his own language that allow mix SQL and imperative constructs:
https://en.wikipedia.org/wiki/Visual_FoxPro
This mean:
* You code login in foxpro
* And the stored procedures
* And the forms
* And the reports
* And the script glues
* ....
"Just" adding SQL/GraphQL to a RDBMS is absolutely not enough. Both are too limited.
For example:
- Can you build a btree with SQL? No
- Work with the terminal? No
- Make a visual grid? No
- etc
Only query and maybe crud.