3 ms·
> As for pervasive NULLs, isn't that more the fault of schema design? I think NULL defaults are widely regarded as a bad thing by now. You should have to decla
by naasking 8y ago
> As for pervasive NULLs, isn't that more the fault of schema design?
I think NULL defaults are widely regarded as a bad thing by now. You should have to declare what's nullable, not declare what's not null.
> There are a lot of things wrong with SQL. Little things like the fact that INSERT and UPDATE have different syntax for no good reason.
Moreover, SELECT should be at the end not the beginning. Query comprehensions and LINQ did this right.
And yes, the implementation inconsistencies are seriously irritating as well.
> Google Cloud Datastore, for instance - it can scale marvellously, but only because it imposes considerable constraints on its queries. Can't we do the same thing with an SQL subset?
If you extend Map-Reduce with a Merge phase, then you can implement the relational algebra with joins [1]. That scales pretty well.
http://cs.brown.edu/courses/cs295-11/mapreducemerge.pdf http://cs.brown.edu/courses/cs295-11/mapreducemerge.pdf
- tomnipotent 8y ago> Moreover, SELECT should be at the end not the beginning. Query comprehensions and LINQ did this right. I'd one-up this and argue that all SQL statements should be in order of execution (within reason). Moving SELECT to the end is definitely a good start.
- nl 8y agoMixing execution concerns and the language seems like a bad idea. It's pretty much impossible to decide what an optimised query should look like on a different databases with different data. Slow network? Fast disks? GPU optimised joins? No way to know what execution order should be, and that's a strength of the relational model.
- MaxBarraclough 8y agoInteresting paper, thanks.