4 ms·
The main problem that I see is that relational model / sql is ALWAYS coupled with RDBMS, even with the proponents of the relational model! The thing is, sql is
by mamcx 8y ago
The main problem that I see is that relational model / sql is ALWAYS coupled with RDBMS, even with the proponents of the relational model!
The thing is, sql is much less capable then even forth. You can't do:
query = where a = ?1
columns = [name, id ]
console.write(columns ?rename name as a |> query)
not even
console.write
not even
Window.open
neither store table in a field (not serializate it, store) create your btree, make open gl game, make a osx app, create a rdbms and so on. (yes, i'm aware some rdbms could, hacking around, kind of do it witth pain)
In short, the relational model is not see as something that can be made for a full language WITHOUT RDBMS.
That is what I wish to change:
http://tablam.org/ http://tablam.org/
because I work before as foxpro developer and see how easy and logical was to work with tables without sql.
- paulddraper 8y agoI agree the relational model can be very useful. I will often keep a lot of queries in the DMBS, or even create a :memory: database with sqlite when I want to use relational logic. Thanks for the link.
- tabtab 8y agoI agree that the integration of domain programming and database programming/querying in FoxPro/xBase created a smoother CRUD-app shorthand that current tools can't match. Less converting of sh8t between the layers (and less need for layers). The newest generation must like to type and read a lot of code, I guess. Or, it's a conspiracy from Carpel Tunnel and eye doctors to get more revenue.